Configuration

Any aspect of TDK operation can be further configured with YAML using the full power of this language, including anchors and aliases.

Firstly, we can get the default configuration running TDK with the dry-run command. In this case, TDK generates configuration based on source database schema and data but doesn’t execute it:

java -jar tdk.jar \
    --input-url jdbc:h2:tcp://localhost:9123/input;DATABASE_TO_LOWER=TRUE --input-username sa \
    --output-url jdbc:h2:tcp://localhost:9124/output;DATABASE_TO_LOWER=TRUE --output-username sa \
    dry-run

And we can create and use our configuration file with our parameters and scenarios:

java -jar tdk.jar \
    --input-url jdbc:h2:tcp://localhost:9123/input;DATABASE_TO_LOWER=TRUE --input-username sa \
    --output-url jdbc:h2:tcp://localhost:9124/output;DATABASE_TO_LOWER=TRUE --output-username sa \
    --config-file config.yaml

For more information, you can check the configuration reference.