[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005169#comment-16005169
]
Emilio Lahr-Vivaz commented on ARROW-999:
-----------------------------------------
Thanks, maybe I should update this issue to be 'implement non-nullable
FieldVectors'? Is that something that would be desirable to implement, or would
it introduce too much complexity? It seems like it would provide a performance
improvement in the non-nullable case.
> [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: Improvement
> Affects Versions: 0.3.0
> Reporter: Emilio Lahr-Vivaz
> Priority: Minor
>
> 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)
