[
https://issues.apache.org/jira/browse/SQOOP-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14277212#comment-14277212
]
Veena Basavaraj edited comment on SQOOP-1976 at 1/14/15 4:52 PM:
-----------------------------------------------------------------
my suggestion for this is store it is array and not as list. I am not sure why
wee need it to ArrayList ( I understand changing it from LinkedList to
ArrayList ) was good, but there is no real benefit with a LIST, If that was
the case we could have stores List<Object> in the IDF as well.
https://issues.apache.org/jira/browse/SQOOP-2011
was (Author: vybs):
my suggestion for this is store it is array and not as list.
> Sqoop2: Avoid massive in-memory copy of schema column
> -----------------------------------------------------
>
> Key: SQOOP-1976
> URL: https://issues.apache.org/jira/browse/SQOOP-1976
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Qian Xu
> Assignee: Qian Xu
>
> SQOOP-1836 introduced a new method {{getColumnsArray}}. As the class
> {{Schema}} is used very often, the idea is to provide a constant (better)
> lookup time for particular column. But I think the implementation will create
> array from a list for every call, it will be even slower than accessing the
> original {{getColumnsList}} in some cases. I think we can change the type of
> columns from {{LinkedList}} to {{ArrayList}}, which is included in
> SQOOP-1969. The jira proposes to remove {{getColumnsArray}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
