We have got a scenario here. We have been pulling data for facebook ads for last 1 year and we realised we want more attributes but we don't want to loose our existing data how do we go about this?

What about: 1. renaming your raw/normalized

_airbyte_raw_ads

and

ads

tables to a different name (

_airbyte_raw_ads_backup

and

ads_backup

for example) 2. re-sync from scratch to recreate

_airbyte_raw_ads

and

ads

tables with more attributes 3. merge the backup tables back into main tables, filling up the new attributes with values as you see fit

Can't we keep raw as it is and start pulling new data as anyways raw is a json string and normalisation handles the new attributes leaving the old one as null or so.

Because pulling all data for last 2 years will be too hectic if we are having 50-100 customers

ah yea you’re right you could do that

just to be safe, make a copy backup just in case while resetting catalogs though

the reset schema tends to flush the raw table empty…

Isn't this a common use case can we create a better way to solve this. Right now even if I click on No need it's resetting both raw and normalised tables.

yes we’ll be working on it, you can follow this issue: https://github.com/airbytehq/airbyte/issues/3520

adding attributes/fields/columns or adding new streams/tables by changing the schema/catalog of a sync is not really well handled at the moment

Sounds great. 👍 will be waiting for it

Right now even if I click on No need it’s resetting both raw and normalised tables

I hope you followed my advice with the backup copy table 😨