[Bug] Nullability validation incorrectly checks children masked by null parents
- 主要语言
- C++
- 星标
- 65
- 派生
- 25
- 平均合并
- 2 天 12 小时
- 30 天内合并 PR
- 80
描述
### Search before asking
- [x] I searched in the [issues](https://github.com/apache/paimon-cpp/issues) and found nothing similar.
### Paimon-cpp version
master
### Minimal reproduce step
`ArrowUtils::CheckNullabilityMatch` recursively checks complete Arrow child arrays.
For nested Arrow types, a null parent may still have physical child values. These
children are logically hidden and should not participate in nullability validation.
However, if a hidden child is null and its field is non-nullable, the current
implementation rejects the batch.
This affects nested STRUCT, LIST, MAP, and VECTOR fields and is inconsistent with
Java's logical row semantics.
### What doesn't meet your expectations?
Expected behavior:
- Ignore child values masked by a null parent.
- Reject null children when the parent is valid and the child is logically visible.
### Anything else?
_No response_
### Are you willing to submit a PR?
- [x] I'm willing to submit a PR!
贡献指南
调研方向
首先定位 ArrowUtils::CheckNullabilityMatch,以及覆盖嵌套 STRUCT、LIST、MAP 和 VECTOR 数组的测试。验证 null 父级包含物理上为 null 的子级的情况,以及有效父级暴露 null 子级的情况;完成的标准是忽略被屏蔽的子级,同时拒绝可见的非 nullable 子级。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- cpp
- 领域
- data-engineering
- Issue 类型
- 缺陷
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 活跃度
- 活跃
- 描述清晰度
- 基本清楚
- 新手友好度
- 58/100