Redshift Connector –Support Target Table Default Values for Missing Columns in Redshift Load Write Method

We would like to request an enhancement to the IBM DataStage Redshift Connector to improve handling of target table columns that contain database-defined default values when using the Load write method.

Currently, all target table columns must be supplied in the incoming metadata and data stream during load operations, even when the target table already defines valid default values for those columns. This behavior creates additional development and maintenance effort and limits the ability to leverage standard database functionality.

Many enterprise data warehouse environments use default values for audit columns, status flags, control indicators, timestamps, surrogate keys, and other common attributes. These defaults are defined at the database level to ensure consistency and reduce the need for application-level logic. However, when using the Redshift Load write method, these database defaults are not automatically utilized when columns are omitted from the incoming data.

Requested Enhancement: Enable the Redshift Connector Load write method to recognize and honor target table default values for columns that are not present in the incoming metadata or data stream. This would allow organizations to fully utilize database-defined defaults and align load behavior more closely with standard database practices.

Business Benefits:

• Reduces development and maintenance effort.

• Improves usability of the Redshift Connector.

• Simplifies migration of existing ETL workloads to Redshift.

• Promotes consistency across different write methods.

• Eliminates the need to explicitly populate columns whose values are already defined by database defaults.