Make inlining configurable based on diff use-case.
Open
area:metadata-table
from-jira
priority:high
type:feature
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
Make inlining configurable based on diff use-case.
Files partition, column_stats and bloom might need inlining. but record level index may not need inline reading.
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-2657
- Type: New Feature
- Epic: https://issues.apache.org/jira/browse/HUDI-1822
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing the linked JIRA issue and the current handling of inlining for partition, column_stats, bloom, and record-level indexes. Done means the inlining behavior can be configured according to the diff use-case, with the intended distinction between file-level and record-level index reads documented or tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100