[Java] Minor types don't account for nullable FieldType flag
- Dominant language
- Java
- Stars
- 94
- Forks
- 152
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 11
Description
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.*
Contributor guide
Research direction
Start at the Java implementation of FLOAT4.getNewVector and inspect how FieldType(false, ...) is interpreted for Float4Vector and NullableFloat4Vector. Trace the FieldVector constraint mentioned in the issue and determine the intended meaning of the nullable flag; done means the returned vector type and top-level vector behavior match that contract.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- data
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100