I have a data source with a few schemas and I want to write them to the same destination schema, but with a source schema prefix. Is that possible?

Yes, this is possible using Airbyte's Custom namespace format combined with the

${SOURCE_NAMESPACE}

dynamic parameter. However, based on your use case — writing multiple source schemas into the same destination schema but with a source schema prefix — the closest approach would be to use a custom namespace format like:

my_${SOURCE_NAMESPACE}_schema

This would create separate destination schemas per source namespace (e.g.,

my_public_schema

), rather than a single schema. [Namespace examples] If you truly want all streams in one destination schema but with the source schema name as a table prefix, Airbyte doesn't natively support per-stream dynamic prefixes based on the source namespace. The Stream prefix setting applies the same static prefix to all streams connection-wide. [Configuring schemas] Here are your practical options: 1. Use a custom namespace per connection — Set the namespace to

${SOURCE_NAMESPACE}

so each source schema maps to its own destination schema. This keeps schemas separated but mirrors the source structure. [Namespace docs] 2. Use a static stream prefix per connection — If you create one connection per source schema, you can assign a unique static prefix (e.g.,

schema1_

) to each connection. This lands all tables in the same destination schema with a distinguishing prefix. [Configuring schemas] 3. Combine downstream — Sync into separate namespaces/schemas and use dbt or your destination's SQL tooling to merge/union the data into a single schema afterward. [Forum discussion] > ⚠️ Note: Airbyte now requires that stream identifiers be unique across connections sharing the same destination. If you use option 2, make sure each connection has a unique prefix or namespace to avoid conflicts. [Airbyte 1.6 release notes] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.