Skip to content

Improve duplicate detection in _plan_partition_changes #52

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

Merged
merged 1 commit into from
May 28, 2022
Merged

Improve duplicate detection in _plan_partition_changes #52

merged 1 commit into from
May 28, 2022

Conversation

jcjones
Copy link
Collaborator

@jcjones jcjones commented May 26, 2022

Fixes #46

The bug was that the partition deduplication only happened against existing
partitions; if we planned to produce two duplicates, because the rates of
change are crazy, then we wouldn't fix them, leaving it for the later
exception to be thrown during SQL generation.

Fixes #46

The bug was that the partition deduplication only happened against existing
partitions; if we _planned_ to produce two duplicates, because the rates of
change are crazy, then we wouldn't fix them, leaving it for the later
exception to be thrown during SQL generation.
@jcjones jcjones merged commit a96b8bb into main May 28, 2022
@jcjones jcjones deleted the 46 branch May 28, 2022 17:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Duplicate Partition Exception when multiple tables are to be renamed
2 participants