[
https://issues.apache.org/jira/browse/SQOOP-1359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071809#comment-14071809
]
Jarek Jarcec Cecho commented on SQOOP-1359:
-------------------------------------------
{code}
-ivy.version=2.1.0
+ivy.version=2.3.0
{code}
I know that it's two line change, but considering that Ivy is crutial part of
the build process, can we make the upgrade in separate JIRA, so that it's
obvious why&when we've changed it?
> Fix avro versions in Sqoop to stop shipping hadoop1 jars with hadoop2
> ----------------------------------------------------------------------
>
> Key: SQOOP-1359
> URL: https://issues.apache.org/jira/browse/SQOOP-1359
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.4, 1.4.5
> Reporter: Venkat Ranganathan
> Assignee: Venkat Ranganathan
> Fix For: 1.4.5
>
> Attachments: SQOOP-1359.patch
>
>
> AVRO-1170 fixed avro-mapred for hadoop2 and we now have avro-mapred hadoop1
> and hadoop2 specific jars. Our dependency should be updated to use the
> right jars. I recently found similar issues with Hive shipping avro-mapred
> hadoop1 jars (HIVE-7240) causing issues in certain integration scenarios.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
