Separate raw tables and normalized tables separately in different schemas

[mdhatrika]

Tell us about the problem you're trying to solve

What are you trying to do, and why is it hard? A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

I set up an integration from HubSpot into the Postgres database I see the tables being generated but both raw and the normalized tables, for suppose I have table owners in HubSpot when I made the connection it is getting both owners and owners_raw table this could cause confusion about which one is the correct table to refer to for other users, and we don't want to maintain 2 different tables in one schema which is not clean

Describe the solution you’d like

A clear and concise description of what you want to see happen, or the change you would like to see

Separate out the raw tables in another schema like Hubspot_Raw schema and normalized tables in HubSpot schema, so other users can only worry or maintain the tables which are under the Hubspot schema

Describe the alternative you’ve considered or used

A clear and concise description of any alternative solutions or features you've considered or are using today.

Additional context

Add any other context or screenshots about the feature request here.

┆Issue is synchronized with this Asana task by Unito

[toandm]

Yes, please add this in. It's really frustrating when the sync has hundreds of tables.
For example we have a connection from MySQL to BigQuery that syncs 900 tables, and the destination schema has 900x2 tables at least. Not to mention scd and dbt_temp tables as well. Too many
Maybe you can dump these raw tables into the default destination schema

[grishick]

@misteryeo FYI, pretty interesting request

[SChalupaBraiins]

I completely agree, temp and raw tables separatation is really needed to provide better services to our users. Best solution for me is to have a some kind of "working schema" setting for all airbyte structures which are not the final output. Structures should be identified by some internal ID and decision of schemas and table names should be offered to ETL creator.

[cgardens]

Done!