You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sqoop.apache.org by "Veena Basavaraj (JIRA)" <ji...@apache.org> on 2015/01/13 00:54:35 UTC
[jira] [Updated] (SQOOP-1936) Ordering of the Sqoop output can be
custom to IDF implementation
[ https://issues.apache.org/jira/browse/SQOOP-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Veena Basavaraj updated SQOOP-1936:
-----------------------------------
Summary: Ordering of the Sqoop output can be custom to IDF implementation (was: Ordering of the Sqoop output is dependent on the IDF text format, is this expected?)
> Ordering of the Sqoop output can be custom to IDF implementation
> ----------------------------------------------------------------
>
> Key: SQOOP-1936
> URL: https://issues.apache.org/jira/browse/SQOOP-1936
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Attachments: SQOOP-1936.patch
>
>
> The compareTo method in SqoopWritable looks like below, this means we are relying on the entire CSVString to order elements in the output.
> For instance, if we have 20 records in JDBC data source, the output will not be ordered by its primary key, especially when we need to do delta merges, we have to be cognizant that the ordering of records in the output is controlled by their CSV representation
> {code}
> String getString() {
> return toIDF.getCSVTextData();
> }
> @Override
> public int compareTo(SqoopWritable o) {
> return getString().compareTo(o.getString());
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)