https://linen.dev logo
#ask-community-for-troubleshooting
Title
# ask-community-for-troubleshooting
b

Bean L

11/30/2021, 12:19 PM
Hey everyone, I am new to Airbyte and just deployed a local dev to load data from postgres to snowflake then transform data there and load the transformed data in snowflake to anther postgres databases for use. I plan to use Airbyte to help me on load data from postgres -> snowflake then snowflake to postgres. Currently I am using basic normalisation option but it is created a _airbyte_raw table then create a expected table I wanted._ Because I wanted to make it just 1-1 mapping. Can I do it in airbyte?
1
u

[DEPRECATED] Augustin Lafanechere

11/30/2021, 3:46 PM
Hi @Bean L, if you want to benefit from basic normalization the raw tables are required because these are the table on which airbyte runs the normalization process.
b

Bean L

11/30/2021, 3:52 PM
yes I know but is there option to skip it? Like I only need to get 1 - 1 mapping and it currently support relational database only.
u

[DEPRECATED] Augustin Lafanechere

11/30/2021, 3:53 PM
You can chose "Raw data - no normalization" in the connection settings
b

Bean L

11/30/2021, 4:14 PM
yes but it will not map data from postgres.schemaA.tableB.fieldC -> snowflake.schemaA.tableB.fieldC.
u

[DEPRECATED] Augustin Lafanechere

11/30/2021, 4:45 PM
Does playing with Namespace configuration and table prefix could help you reach this?
b

Bean L

11/30/2021, 4:56 PM
it does not help. If I set no basic transformation was set it just do at normal load. with 3 _airbyte field - json format. I know airbyte is built for general loading data but here is the case to load data between relational database still can’t not map a table to a table with nearly same schema is weird everything need to go back to json format.
u

[DEPRECATED] Marcos Marx

12/02/2021, 12:10 AM
yes I know but is there option to skip it?
Like I only need to get 1 - 1 mapping and it currently support relational database only.
No, Airbyte will transform your data to Airbyte Protocol. In some cases you won't have the same data type at your destination even if you're doing Postgres to Postgres.