[
https://issues.apache.org/jira/browse/SQOOP-2011?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Veena Basavaraj updated SQOOP-2011:
-----------------------------------
Description:
it is asking for trouble to store the schema columns in array and expose a
list. the matching code currently uses LIST and it can completely use the array
and work with it. In all places in IDF code we use the column array via the
index.
Array is preferred since it is easier to walk thorugh the object array format,
there is one-one correspondence between the two with indexes
http://eclipsesource.com/blogs/2014/04/11/3-good-reasons-to-avoid-arrays-in-java-interfaces/
Please read the UPDATE section in the above link:) We really do not need the
abilities of a list, we know the only reason we will use schema columns is
read only.
was:
it is asking for trouble to store the schema columns in array and expose a
list. the matching code currently uses LIST and it can completely use the array
and work with it. In all places in IDF code we use the column array via the
index.
Array is preferred since it is easier to walk thorugh the object array format,
there is one-one correspondence between the two with indexes
> Schema should expose columns in array or list and not both
> ----------------------------------------------------------
>
> Key: SQOOP-2011
> URL: https://issues.apache.org/jira/browse/SQOOP-2011
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Fix For: 2.0.0
>
>
> it is asking for trouble to store the schema columns in array and expose a
> list. the matching code currently uses LIST and it can completely use the
> array and work with it. In all places in IDF code we use the column array via
> the index.
> Array is preferred since it is easier to walk thorugh the object array
> format, there is one-one correspondence between the two with indexes
> http://eclipsesource.com/blogs/2014/04/11/3-good-reasons-to-avoid-arrays-in-java-interfaces/
> Please read the UPDATE section in the above link:) We really do not need the
> abilities of a list, we know the only reason we will use schema columns is
> read only.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
