You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@arrow.apache.org by "Li Jin (JIRA)" <ji...@apache.org> on 2017/11/07 19:19:00 UTC
[jira] [Comment Edited] (ARROW-1710) [Java] Decide what to do with
non-nullable vectors in new vector class hierarchy
[ https://issues.apache.org/jira/browse/ARROW-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16242687#comment-16242687 ]
Li Jin edited comment on ARROW-1710 at 11/7/17 7:18 PM:
--------------------------------------------------------
Seems we agree to remove non nullable vectors.
The next question is, what do people feel about dropping the "Nullable" prefix in new vector classes? [~bryanc] brought this up initially.
I am +1 for dropping the "Nullable" prefix. I think It makes the code more concise.
was (Author: icexelloss):
Seems we agree to remove non nullable vectors.
The next question is, what do people feel about dropping the "Nullable" prefix in new vector classes? [~bryanc] brought this up initially.
I am +1 for dropping the "Nullable" prefix. It makes the code more concise.
> [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)