@kapa.ai Is there a way to enforce respect for column order when using Redshift as a source?

No. Based on the available information, Airbyte does not guarantee preserving the source column order in downstream representations (UI, catalog display, or destination table creation), even if the source connector itself outputs columns in a specific order. In particular: - A user building a custom source connector (Oracle) confirmed that although the

CATALOG

message contained fields in the desired order, the UI and the created destination table reordered the columns anyway; the GitHub issue is still closed with no fix referenced. [[Field order issue](https://github.com/airbytehq/airbyte/issues/48829)] - Another user syncing from Google Sheets to BigQuery asked for preserving column order, and the official response was that preserving source column order is not supported and is not treated as a bug. [[Column order forum](https://discuss.airbyte.io/t/2865)] The Redshift source docs similarly emphasize that schema may be altered depending on the destination and do not mention any option to preserve or enforce column order. [[Redshift source](https://docs.airbyte.com/integrations/sources/redshift#overview)] So, with Redshift as a source, there is currently no documented way in Airbyte to enforce that column order is respected end‑to‑end.