[
https://issues.apache.org/jira/browse/ARROW-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16220392#comment-16220392
]
Ethan Levine commented on ARROW-1710:
-------------------------------------
[~jnadeau]: I'd be interested to learn more about that consolidation. It sounds
like the validity bits will be stored inline with the data? It seems like
eliding that could be difficult.
Our use case involves data that's mostly not nullable, and we take care to
ensure that it's declared that way. If the costs of writing only non-null
values to a nullable array (in terms of memory and computation) become
insignificant, then it makes sense to only include nullable arrays. But if
that's not the case then I think it makes sense to keep both.
> [Java] Decide what to do with non-nullable vectors in new vector class
> hierarchy
> ---------------------------------------------------------------------------------
>
> Key: ARROW-1710
> URL: https://issues.apache.org/jira/browse/ARROW-1710
> Project: Apache Arrow
> Issue Type: Sub-task
> Components: Java - Vectors
> Reporter: Li Jin
> Fix For: 0.8.0
>
>
> So far the consensus seems to be remove all non-nullable vectors.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
