[to be discussed] Hive sync clients should publish current HUDI version to HMS
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
### Task Description
**What needs to be done:**
Update HoodieHiveSyncClient and HiveSyncTool publish semver of current HUDI build to HMS
**Why this task is needed:**
When orchestrating table service jobs for datasets, we need to get current version of HUDI build used by the client that writes records to the dataset. Since this is needed to infer which HUDI build to use in the table service job, to account for breaking changes between major version releases.
### Task Type
Code improvement/refactoring
### Related Issues
**Parent feature issue:** (if applicable )
**Related issues:**
NOTE: Use `Relationships` button to add parent/blocking issues after issue is created.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading HoodieHiveSyncClient and HiveSyncTool, then trace how they publish metadata to HMS. Determine where the current HUDI build's semver should be exposed and verify that HMS contains it for clients using both sync entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100