-
Notifications
You must be signed in to change notification settings - Fork 4.8k
HIVE-28655: Implement HMS Related Drop Stats Changes (Part2) COL_STATS_ACCURATE related changes #6198
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
base: master
Are you sure you want to change the base?
Conversation
|
…AT_ACCURATE After Dropping
… COL_STATS_ACCURATE related changes
6bed69f to
61539a6
Compare
|
| } | ||
|
|
||
| // Serialize the map into a new JSON string | ||
| String updatedValue = mapper.writeValueAsString(statsMap); |
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.
use StatsSetupConst.removeColumnStatsState?
soumyakanti3578
left a comment
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.
Added a few comments here, but I also noticed that I had reviewed the earlier version of this PR: #5790
Please go through the review comments there too.
Also it would be nice to go through the sonar report and fix the ones that make sense. For example, there are many reports on code conventions that you should incorporate to improve maintainability and consistency.



What changes were proposed in this pull request?
We need a way to drop the stats associated with the table/partition and its columns.
This can help a lot in migration or replication where the stats data take huge time to copy.
Particularly when the table is partitioned, we have stats rows for each table, partition, column combination, which can get huge when the number of partitions is huge.
This is the HMS side changes.
This is the part2 with the parameter COL_STATS_ACCURATE related changes.
Why are the changes needed?
This can give the users potential options to clear the unnecessary stats.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Manual tests and unit tests.