[
https://issues.apache.org/jira/browse/SQOOP-1936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14274723#comment-14274723
]
ASF subversion and git services commented on SQOOP-1936:
--------------------------------------------------------
Commit 7631d293335855fd42a319c1fcb56530c27f78a4 in sqoop's branch
refs/heads/sqoop2 from [~abec]
[ https://git-wip-us.apache.org/repos/asf?p=sqoop.git;h=7631d29 ]
SQOOP-1936: Sqoop2: Sort by comparing IDF data in shuffle phase
(Veena Basavaraj via Abraham Elmahrek)
> Sqoop2: Sort by comparing IDF data in shuffle phase
> ---------------------------------------------------
>
> Key: SQOOP-1936
> URL: https://issues.apache.org/jira/browse/SQOOP-1936
> Project: Sqoop
> Issue Type: Sub-task
> Reporter: Veena Basavaraj
> Assignee: Veena Basavaraj
> Fix For: 1.99.5
>
> Attachments: SQOOP-1936-v2.patch, SQOOP-1936-v3.patch,
> 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)
