Control S3 destination column order
S3 path mappings can set parser.columnOrder to control the order of payload fields in newly created destination tables.
S3 path mappings can now set parser.columnOrder for payload fields when Artie creates destination tables. Configured metadata columns remain first, helping teams whose downstream workflows depend on a predictable schema order.
Why this matters
- Choose the order of mapped fields in new destination schemas
- Preserve the native field order available for ACH mappings