Skip to content

Conversation

lokeshj1703
Copy link
Contributor

Describe the issue this Pull Request addresses

Closes #14068 #14068

Summary and Changelog

If the min and max file group count for record index is configured and set to the same value, record index records should will not be persisted. We would use the configured value as the file group count instead of estimating it in such a case.

Impact

PR adds an optimisation where record index records will not be persisted if file group count is configured by the user. Also the record index records were not unpersisted after bootstrap. The PR adds unpersist after bootstrap of record index partition.

Risk Level

Low

Documentation Update

NA

Contributor's checklist

  • Read through contributor's guide
  • Enough context is provided in the sections above
  • Adequate tests were added if applicable

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

hudi-bot commented Oct 9, 2025

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

Verified locally that persist and unpersist is working as expected

@lokeshj1703 lokeshj1703 marked this pull request as ready for review October 13, 2025 09:35
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.

Persist RLI index bootstrap records only if estimation is required and add unpersist

2 participants