Bug report Environment: Airbyte hosted, standard container, Postgres<>BigQuery connection Steps to reproduce: 1. Starting state:

normalized tabular data

is toggled; tables are fully synced. 2. I edit the

Replication

settings and remove a stream from my connection 3. A few minutes later, observe that

Raw data (JSON)

is toggled in the Transformation tab. This is concerning because I don't know the state of my data (whether it's normalized or not), or why the transformation setting has reverted to

Raw data (JSON)

. Thank you for your help.

Hi Peter, please make sure to review the code of conduct: tagging individual team members goes against it. Rule 7: Don't spam tags, or use @here or @channel. Using the @here and @channel keywords in a post will not help, as they are disabled in Slack for everyone excluding admins. Nonetheless, if you use them we will remind you with a link to this rule, to help you better understand the way Airbyte Slack operates. Do not tag specific individuals for help on your questions. If someone chooses to respond to your question, they will do so. You will find that our community of volunteers is generally very responsive and amazingly helpful! We use GitHub to keep track of bug reports and feature requests. If you post a bug report in this Slack channel, it is likely to get lost. Could you please create a GitHub issue? Issues created by the community are sent over to my team and then we triage them into the appropriate team's backlog. If it has to do with a Generally Available connector, these issues are prioritizes; if it has to do with an alpha or beta connector, we encourage the community to contribute a PR as those connectors are not prioritized. I hope this gives you an insight into our process.

I've created a Github Issue here: https://github.com/airbytehq/airbyte/issues/22564