Support nested fields as mandatory columns in flink sql
Open
from-jira
priority:high
status:pr-available
type:improvement
- Dominant language
- Java
- Stars
- 6.2k
- Forks
- 2.5k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 111
Description
Users should be able to use nested field as primaryKey and preCombineField.
Since Spark allows for nested fields to be used for primaryKey and precombineField, Flink should also be consistent with such constraints.
## JIRA info
- Link: https://issues.apache.org/jira/browse/HUDI-5004
- Type: Improvement
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names Flink SQL primaryKey and preCombineField constraints but no source files, tests, or entry points. Compare the existing Spark behavior with Flink's handling of these fields, then verify that nested fields are accepted for both cases and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, sql
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100