[Java] Minor types don't account for nullable FieldType flag
- 主要语言
- Java
- 星标
- 94
- 派生
- 152
- 平均合并
- 3 天 16 小时
- 30 天内合并 PR
- 11
描述
Calling e.g. `FLOAT4.getNewVector("foo", new FieldType(false, ...), ...)" returns a NullableFloat4Vector instead of a Float4Vector.
edit: Float4Vector doesn't implement FieldVector, so can't currently be a top-level vector. I'm confused as to what the nullable flag is supposed to represent then.
**Reporter**: [Emilio Lahr-Vivaz](https://issues.apache.org/jira/browse/ARROW-999) / @elahrvivaz
**Note**: *This issue was originally created as [ARROW-999](https://issues.apache.org/jira/browse/ARROW-999). Please see the [migration documentation](https://github.com/apache/arrow/issues/14542) for further details.*
贡献指南
调研方向
从 FLOAT4.getNewVector 的 Java 实现开始,检查 FieldType(false, ...) 对 Float4Vector 和 NullableFloat4Vector 的解释方式。追踪 issue 中提到的 FieldVector 约束,并确定 nullable 标志的预期含义;当返回的向量类型和顶层向量行为符合该契约时,即表示完成。
由索引模型根据 Issue 内容生成。
评估
- 技术栈
- java
- 领域
- data
- Issue 类型
- 缺陷
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 活跃度
- 停滞
- 描述清晰度
- 基本清楚
- 新手友好度
- 30/100