-
Notifications
You must be signed in to change notification settings - Fork 87
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
Mapping Flow from Old [HMS] to new [UC] For External Tables #354
Comments
Dependencies:
|
Probably we would need to have the workspace id/name in the mapping as it can happen to have the same database name between workspaces. thus creating a conflict |
Need to detect conflicts and dedupe. #335 |
@pohlposition let's merge newer issues into older issues :) |
@pohlposition :thinks realistically, we need to have an out-of-band job that can "move" objects to new catalogs. Because you're going to register a table in CATALOG.SCHEMA (A), and then realize later that it doesn't belong there for other workspaces that were referencing it. |
closing in favor of #669 |
Database / Schema > UC Catalog
Database may map to 1 or more Catalogs
Defined Table Migration Process defined in this PR: #307
Probably a file that someone downloads, modifies, and uploads (offline mapping)
The text was updated successfully, but these errors were encountered: