Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[HUDI-8232] Adding Index defn for Col stats to track the list of columns indexed #12529
base: master
Are you sure you want to change the base?
[HUDI-8232] Adding Index defn for Col stats to track the list of columns indexed #12529
Changes from 2 commits
a323593
6377822
1eaf510
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
This check is costly. If not for this check, then we don't need
mdtCommitMetadata
and hence don't need to create mdtMetaClient and deserialize the instant. If we strictly need this check, please consider caching the meta client or reusing an existing instance if possible.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.
This is more of a defensive check. what incase nothing gets written to col stats partition even though write config and table property say so. So, just wanted to make sure we have successfully written data to col stats partition. before we can update the index defn.
Also, our metadata writer is short lived. we create a new one, apply a commit metadata and close it out. So, the data table write client does not have any metadata meta client for us to re-use here unfortunately.
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.
how are nested fields getting tracked? Is it like
a.b
? Asking bcoz if a nested field has same name as any other non-nested field, then equals check could return unexpected result.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.
yes, good point. we might have to split by comma and then compare the lists.
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.
actually, its already taken care.
this is in HoodieTableMetaClient.buildColSatsIndexDefinition
so, its already list of strings comparison. So, we should be good
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.
If we're anyway going to check and update post commit, why doing it here?
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.
just that, if initialization succeeded, but before applying the commit of interest if job crashed. we don't want to miss the index defn update.
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.
essentially, for regular commits, both mdt write and data table write has to complete and we update the index defn.
but for initialization, its a special commit, once mdt commit is completed, readers are eligible to read the data. and hence its better to keep the index defn in sync.
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.
what happens when
populateMetaFields
is disabled? Should we still error out?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.
nope. why. we should just skip indexing meta field if populateMetaFields is false.
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.
So, already its accounted for.
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.
how about rename to
createOrUpdateColumnStatsIndexDefinition
? The method is not actually creating/updating the stats right.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.
👍