Handling Duplicated Column Names in Airbyte

Summary

Inquiry about Airbyte’s handling of duplicated column names after standardization and whether users can choose the behavior for exclusion or selection.


Question

Also unrelated, how does Airbyte handle duplicated column names at source after standardization? Can users choose the behavior - exclude both, pick one, etc? (e.g. SecRegion_c vs Sec_Region__c both map to sec_region_c). Currently using a vendor and unhappy with the lack of options.



This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['duplicated-column-names', 'standardization', 'user-options', 'airbyte']