[
https://issues.apache.org/jira/browse/ARROW-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16193006#comment-16193006
]
ASF GitHub Bot commented on ARROW-1473:
---------------------------------------
Github user jacques-n commented on the issue:
https://github.com/apache/arrow/pull/1164
@icexelloss: My preference is also to avoid having separate int and
nullable int vectors. Only have NullableIntVector. As far as duplication goes,
I think the second commit here seems to be small enough number of things that
we could skip the templates and just manage a little more code.
@elahrvivaz I'm not entirely clear on how the casting helps with generics.
one of the holder methods could be made to follow this pattern. Can you provide
an example pattern where the generic setter will help avoid any casting? (Or
are you just talking about less casting?) We built the reader/writer interfaces
specifically to avoid casting (in cases where people don't use generated code).
> [JAVA] Create Prototype Code Hierarchy (alt A)
> ----------------------------------------------
>
> Key: ARROW-1473
> URL: https://issues.apache.org/jira/browse/ARROW-1473
> Project: Apache Arrow
> Issue Type: Sub-task
> Reporter: Jacques Nadeau
> Assignee: Siddharth Teotia
> Labels: pull-request-available
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
