[c6d6]

How does it handle schema drift (eg saas vendor changes a column)? Does the annotation agent mark breaking changes in some way or just describe the current state of the world? With that many connections, you'll hit a bunch of weird edge cases, especially with things like salesforce custom objects.

[Kappa90]

Right now schema changes create new columns, I’m working on reconciling old columns, which right now are not dropped.

The annotation/semantic layer agent creates a new description of the schema on sync, which represents the current state, but that includes stale columns as of today, data is not dropped.

I’ll implement automated schema migrations in the next week or so!