async generator raised StopAsyncIteration after changing database reference for an existing connector

[ppf2]

A user reported an async generator raised StopAsyncIteration error when using MSSQL against Microsoft SQL Azure (RTM) after switching the database name in the connector configuration and re-running the sync.

We suspect that this is due to the two data sources not having the same data structure.

As part of our investigation, a recommendation was made:

The advice is to use only one data source per connector. If they indexed some data and they want to change the data source they need to create a new connector or make sure the new data source has the same data.

If this is the best practice, it will be helpful to build some guardrails (for all of our database connectors) to prevent users from switching the data source (if the data scheme is different) and return the appropriate error handling to ask the user to create a new connector instead. Thx!