Error table default behavior

cgiles · July 6, 2021, 6:08pm

🙋 Feature Request:

Change default behavior to not create or populate an error table. Include a flag to utilize this feature if desired.

Expected Behavior:

If data loader is run, no error table creation or population will be attempted. If error_table switch is added and provided a table name then this feature will be utilized.

Current Behavior:

Error table is created and populated by default

💁 Possible Solution:

Remove default behavior and add a switch

Context:

Examples / Screenshots:

gennady · July 15, 2021, 9:03pm

@cgiles thank you for the feature request. We’ve received this request previously, but as you can appreciate, changing default behavior isn’t something we can do lightly as it may impact multiple customers and use cases. Allow us some time to investigate this request.

cgiles · July 21, 2021, 7:15pm

@gennady In the mean time do we want to consider implementing a flag that would disable the error table functionality?

gennady · July 23, 2021, 7:36pm

We’re going to change the default behavior instead in next major release.

gennady · November 22, 2021, 8:04pm

@cgiles I’m happy to announce that Data Loader 3.0.0 is officially released and has a lot of great enhancements in the new version.

One of the changes is related to this request. So starting with this version, the logging to an error table functionality is no longer the default as it now requires the explicit use of the log_to_error_table flag.