Option to Disable reserved_incorta_extraction_timestamp for New Tables and Materialized Views

[Matt2]

Hello Incorta Community,

My organization would like to submit an enhancement request regarding the automatic creation of the reserved_incorta_extraction_timestamp column during table creation.

Following our recent upgrade of the Development environment, our QA team observed that newly created physical tables automatically include the reserved_incorta_extraction_timestamp column. After reviewing this behavior with Incorta Support under Request #69820, we were informed that the functionality is currently working as designed and that the ability to disable or remove this column would require a product enhancement.

While we understand the purpose of the extraction timestamp for data lineage and auditing, not all use cases require this column. In some scenarios, the automatically generated column:

• Creates confusion for developers and business users during table creation.
• Introduces unnecessary columns into datasets where extraction tracking is not required.
• Requires additional effort to explain or work around during development and QA activities.
• Results in inconsistent behavior between physical tables and Materialized Views, which currently appear to behave differently.

Provide administrators or developers with the ability to:

1. Enable or disable automatic creation of the reserved_incorta_extraction_timestamp column.
2. Configure the behavior globally at the environment level or individually at the table level.
3. Optionally hide or exclude the column from the default column list when not required.
4. Ensure consistent and documented behavior across physical tables and Materialized Views.

This enhancement would provide greater flexibility for organizations that do not require extraction timestamp tracking on all datasets while reducing user confusion and improving the table creation experience.

Thank you for your consideration. We would appreciate review by the Product and Engineering teams and any updates regarding roadmap consideration for this enhancement.

Regards,
Matt Lomicka