[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005137#comment-16005137
]
Jacques Nadeau commented on ARROW-999:
--------------------------------------
You probably need to update the vectors so that they set all the bits to null
if they have "no-nulls". The goal was to only have nullable types in the java
implementation as we found maintaining two parallel sets of vectors an extra
level of complexity.
> [Java] Minor types don't account for nullable FieldType flag
> ------------------------------------------------------------
>
> Key: ARROW-999
> URL: https://issues.apache.org/jira/browse/ARROW-999
> Project: Apache Arrow
> Issue Type: Bug
> Affects Versions: 0.3.0
> Reporter: Emilio Lahr-Vivaz
> Assignee: Emilio Lahr-Vivaz
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
