<@U04SE163WC8> I have a connection between mysql (...
# ask-ai
j
@kapa.ai I have a connection between mysql (v3.7.1) and snowflake (v3.11.11) with airbyte version 0.63.13. There are non breaking schema changes detected, where a.o new tables are added. When i save these changes, the review changes pop-up is stil visible and the new tables are not added to the connection. The problem is similar to the following github issue, but I have a newer airbyte version: https://github.com/airbytehq/airbyte/issues/30093
u
Based on the knowledge sources provided, it seems like you're experiencing an issue similar to the one discussed in this [Github issue](https://github.com/airbytehq/airbyte/issues/23349). The issue is about non-breaking schema changes being detected as false positives. In this case, the notification for non-breaking schema changes stays up, however, when going through the schema change review process, no changes are detected. This issue was confirmed by several contributors and was eventually closed, indicating that a solution was found. The process to review detected non-breaking schema changes is outlined in the [Airbyte documentation](https://docs.airbyte.com/using-airbyte/schema-change-management#review-detected-non-breaking-schema-changes). According to the documentation, you need to manually approve any detected schema changes for the schema in the destination to change. However, there are some observations and improvements suggested in this [Github issue](https://github.com/airbytehq/airbyte/issues/26348) that might be relevant to your case. Some users have reported that after clicking on “review changes” and then clicking “OK” in the modal, they think the change has been applied, so they navigate to another screen and see the modal “discard changes”. If you're still experiencing the issue, it might be worth raising a new issue on the [Airbyte Github](https://github.com/airbytehq/airbyte/issues) to get help from the community and the Airbyte team.
j
@kapa.ai This is not an issue of false positives, since there actually are schema changes. The problem is that when accepting and saving the schema changes, they are not saved. It seems like a bug
u
A message from kapa.ai
u
I see, it seems like you're experiencing a bug where the schema changes are not being saved even after accepting and saving them. This is indeed different from the false positive issue. Unfortunately, the provided knowledge sources do not contain a direct solution or workaround for this specific issue. As a next step, I would recommend creating a new issue on the [Airbyte Github](https://github.com/airbytehq/airbyte/issues) detailing your problem. Be sure to include all relevant information such as the Airbyte version you're using, the connectors involved, and the exact steps you're taking when the issue occurs. This will help the Airbyte team and the community to better understand and address your issue.