Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-detect and migrate new schemas in source DB #1037

Closed
sjlogan opened this issue Nov 20, 2020 · 2 comments
Closed

Auto-detect and migrate new schemas in source DB #1037

sjlogan opened this issue Nov 20, 2020 · 2 comments
Labels
area/connectors Connector related issues team/db-dw-sources Backlog for Database and Data Warehouse Sources team type/enhancement New feature or request

Comments

@sjlogan
Copy link

sjlogan commented Nov 20, 2020

I am trying to move data from a multi tenant application to a data warehouse. In the source database, each tenant has its own db schema and tables. All of the tables in each tenant's schema match the other schemas. As we add new tenants, we need to manually configure new migrations (or update existing ones) in whatever EL(T) tool we use.

It would be AMAZING if an EL(T) tool could auto-detect new schemas in the source db and automatically migrate all of the data in them to the destination. It would be MORE AMAZING if an EL(T) tool could auto-detect new schemas in the source db and create a matching migration configuration to an existing schema and then use to automatically start data migration.

I could also see a world where an Airbyte API could be triggered on our end when we create a new schema in our source DB that allows me to create a matching migration configuration to an existing schema.

The only way I have been able to get around this problem is manually configuring existing migration logic in other tools to account for each new schema in the source db.

┆Issue is synchronized with this Asana task by Unito

@sjlogan sjlogan added the type/enhancement New feature or request label Nov 20, 2020
@cgardens
Copy link
Contributor

Hi @sjlogan everything you've asked for here makes sense to me! This is definitely in line with our vision. We will keep you posted as we iterate towards these goals. Our focus is on pushing out incremental syncs as a feature now, but schema migration is a top priority after that.

@marcosmarxm
Copy link
Member

This was solved by #17520

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/connectors Connector related issues team/db-dw-sources Backlog for Database and Data Warehouse Sources team type/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

5 participants