Some configuration properties are currently mandatory although they apply to some scenarios only. As a result, the configuration files are more complicated than necessary. Here is a list of these properties and suggested actions to take.
savepoints Used only for CQL, but not relevant for Alternator/DynamoDB. This property should be optional and only the CQL migrator should require it to be present. Unless we plan to support support savepoints for Alternator. In such a case we should keep it mandatory.
skipTokenRanges Used only for CQL in the case of a resumed migration. This property should be optional. It is anyway not intended to be filled by the users.
renames Even if we don’t perform renames, this property is mandatory. I think it should just be optional.
validation This property is only used by the Validator. It should not be mandatory when we run the Migrator.
Some configuration properties are currently mandatory although they apply to some scenarios only. As a result, the configuration files are more complicated than necessary. Here is a list of these properties and suggested actions to take.
savepointsUsed only for CQL, but not relevant for Alternator/DynamoDB. This property should be optional and only the CQL migrator should require it to be present. Unless we plan to support support savepoints for Alternator. In such a case we should keep it mandatory.skipTokenRangesUsed only for CQL in the case of a resumed migration. This property should be optional. It is anyway not intended to be filled by the users.renamesEven if we don’t perform renames, this property is mandatory. I think it should just be optional.validationThis property is only used by the Validator. It should not be mandatory when we run the Migrator.