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

[HUDI-8386] Fix update for secondary index and corresponding validation in metadata table validator #12119

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

lokeshj1703
Copy link
Contributor

Change Logs

The Jira adds update validation for secondary index in metadata table validator. It also makes a fix in update logic and checks for secondary key instead of record key. The earlier logic was leading to some records getting skipped.

Impact

NA

Risk level (write none, low medium or high below)

low

Documentation Update

Describe any necessary documentation update if there is any new feature, config, or user-facing change. If not, put "none".

  • The config description must be updated if new configs are added or the default value of the configs are changed
  • Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
    ticket number here and follow the instruction to make
    changes to the website.

Contributor's checklist

  • Read through contributor's guide
  • Change Logs and Impact were stated clearly
  • Adequate tests were added if applicable
  • CI passed

@github-actions github-actions bot added the size:S PR with lines of changes in (10, 100] label Oct 17, 2024
Copy link
Member

@codope codope left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix! Could you please add an e2e test in TestSecondaryIndexPruning to show where update of secondary index fails?

Comment on lines +285 to +288
Set<String> recKeys = validator.getFSSecondaryKeyToRecordKeys(new HoodieSparkEngineContext(jsc, sqlContext), basePath,
metaClient.getActiveTimeline().lastInstant().get().getTimestamp(), "not_record_key_col", Collections.singletonList(secKey))
.get(secKey);
assertEquals(Collections.singletonList(recKey), recKeys);
assertEquals(Collections.singleton(recKey), recKeys);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this intended change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes this is intended

@hudi-bot
Copy link

CI report:

Bot commands @hudi-bot supports the following commands:
  • @hudi-bot run azure re-run the last Azure build

@lokeshj1703
Copy link
Contributor Author

There is an e2e test in TestHoodieMetadataTableValidator which is reproducing the failure. Also fixed TestSecondaryIndexPruning. The tests were checking an older state of the table so were passing without the fix. After the update fix, had to fix the test to check the latest state of the table.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size:S PR with lines of changes in (10, 100]
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants