hudi
hudi copied to clipboard
[HUDI-7758] Only consider files in Hudi partitions when initializing MDT
Change Logs
- Only considers files in Hudi partitions for MDT to avoid any parsing issues
Impact
- Avoids runtime exceptions trying to parse information from file paths
Risk level (write none, low medium or high below)
None
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
@KnightChess
I think such handling should be maintained on the XTable side, not on the Hudi side.
Probably true, but keeping the files scoped in Hudi itself still make sense for Hudi table, I guess it is hard to fix on XTable side because the metadata table is kind of an inner component.
CI report:
- 09e49d7c4856c6baf4089b538784f2d6cc7b143a Azure: SUCCESS
Bot commands
@hudi-bot supports the following commands:@hudi-bot run azurere-run the last Azure build