[ 
https://issues.apache.org/jira/browse/SQOOP-1976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Qian Xu updated SQOOP-1976:
---------------------------
    Description: 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}}.  (was: 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 slower than accessing {{getColumnsList}}. SQOOP-1969 has already changed the 
columns from {{LinkedList}} to {{ArrayList}}, there is not necessary to have a 
{{getColumnsArray}} anymore.)

> 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: Improvement
>            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)

Reply via email to