-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
HIVE-26000: DirectSQL to prune partitions fails with postgres backend for Skewed-Partition tables #3073
Conversation
…nd for Skewed-Partition tables
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Change looks good to me.
@kgyrtkirk We already have testcase covering this scenario(list_bucket_dml_4.q), but directSql failure happens only with postgres db if column is not quoted. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The fix looks reasonable to me so if it is tested locally I am fine merging this to master. Other than that having tests are good so following up on @kgyrtkirk comment I logged HIVE-26005. It would be nice to tackle this at some point but not necessarily as part of this PR.
Thanks for the review @zabetak. I verified the fix locally. |
please close this as I have merged to master this morning. |
What changes were proposed in this pull request?
PartitionPruning via directSql is failing in postgres db for skewed tables
Why are the changes needed?
Fallback to ORM is taking long time
Does this PR introduce any user-facing change?
No
How was this patch tested?
We already have a testcase covering the issue (list_bucket_dml_4.q), it happens in postgres backend db.