At present, migration-tool's load utility fails, after spending quite some time processing, if one of the tables does not have a corresponding .csv file in the specified directory.
Instead of failing, it should simply note the fact and go ahead with other import. Or, there should be an option provided to ignore certain tables from the import.
It is possible, that one would want to use migration tool to import a subset of tables from another DB system. Or, a manual work around may require to re-import just one or two tables.
At present, migration-tool's load utility fails, after spending quite some time processing, if one of the tables does not have a corresponding .csv file in the specified directory.
Instead of failing, it should simply note the fact and go ahead with other import. Or, there should be an option provided to ignore certain tables from the import.
It is possible, that one would want to use migration tool to import a subset of tables from another DB system. Or, a manual work around may require to re-import just one or two tables.