[jira] [Commented] (SQOOP-1936) Ordering of the Sqoop output is dependent on CSVString, is this expected?

["Veena Basavaraj (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SQOOP-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268686#comment-14268686 ] 

Veena Basavaraj commented on SQOOP-1936:
----------------------------------------

[~jarcec] would you mind answering this? we should have this controlled by IDF since always using csv text string to compare is not ideal and will give us no way to acheive a grouping or ordering we may want to.

> Ordering of the Sqoop output is dependent on CSVString, is this expected?
> -------------------------------------------------------------------------
>
>                 Key: SQOOP-1936
>                 URL: https://issues.apache.org/jira/browse/SQOOP-1936
>             Project: Sqoop
>          Issue Type: Sub-task
>            Reporter: Veena Basavaraj
>
> 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)