Description
Describe the feature
Currently, the construct is based around the name of a table column being fixed, however redshift enables the user to change the name of the table columns, if needed.
Use Case
If we have an existing column name that is not distinctive enough, further columns added in the future might "clash" with the "meaning" behind the original table column.
Proposed Solution
Possibly by implementing an extra id
attribute to the existing Column
construct. However this would require a possible refactor to the checking conditions that already exist, due to the name
attribute being used currently. This is definitely NOT a critical change, and infra developers could currently alleviate this problem by using the AWS console, and reworking their tables from there.
However, if this is implementable by just a simple addition of an id
attribute, then this would be a good step in the right direction I believe for the Redshift Construct.
Other Information
No response
Acknowledgements
- I may be able to implement this feature request
- This feature might incur a breaking change
CDK version used
2.56.0
Environment details (OS name and version, etc.)
Amazon Linux 2
Activity