[
https://issues.apache.org/jira/browse/ARROW-999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16005908#comment-16005908
]
Jacques Nadeau commented on ARROW-999:
--------------------------------------
I've previously found that it adds excessive complexity (earlier versions of
Arrow maintained them more as alternatives to the nullable versions). We've
generally found that once you do vectorized operations, word-wise or wider
bitmap evals are rarely the performance bottleneck.
> [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)
