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

Prevent the forward-only categorization of changes that require the creation of a new physical table #1956

Open
izeigerman opened this issue Jan 10, 2024 · 0 comments
Labels
Improvement Improves existing functionality

Comments

@izeigerman
Copy link
Member

Currently there are no limitations on what can be changed as part of the forward-only plan / model. This includes model attributes that might require the creation of a new physical table or more advanced ALTER TABLE statements that are currently not supported as part of the table migration process. Some of such attributes include:

  • storage_format
  • partitioned_by
  • clustered_by
  • table_properties
  • default_catalog

We should make sure that changes to these properties can't be categorized as forward-only.

@izeigerman izeigerman added the Improvement Improves existing functionality label Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Improvement Improves existing functionality
Projects
None yet
Development

No branches or pull requests

1 participant