Refreshing the source schema destroys connection config

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Amazon Linux
  • Memory / Disk: 8 Gb / 20 Gb
  • Deployment: Docker
  • Airbyte Version: 0.38.4-alpha
  • Source name/version: Microsoft SQL Server (MSSQL) 0.3.22
  • Destination name/version: Snowflake 0.4.26
  • Step: Refresh Source Schema
  • Description: Refreshing the source schema destroys connection config. When clicking Refresh Source Schema, Airbyte successfully discovers the most recent schema including any schema changes. The existing config is conserved after refreshing and Airbyte allows for changing the replication config by adding tables, tec. However, upon clicking “save change & reset data” and clicking through the pop up (see attached image), all connector config is reset and the schema appears empty. It appears that Airbyte completely resets the connector without any config or schema and is only recoverable by refreshing the schema again and re-configuring the settings.

Hey thanks for reporting. You can track this here

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.