[
https://issues.apache.org/jira/browse/SQOOP-1198?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812515#comment-13812515
]
Jarek Jarcec Cecho commented on SQOOP-1198:
-------------------------------------------
I've took a deep dive into the issue and I believe that I found the culprit.
Interestingly with or without attached patch, when building against Hadoop
2.1.0, ivy will correctly use protobuf 2.5.0 for both compile and test step.
Yet the running the tests without the patch will fail on an exception that is
suggesting different protobuf version. I've noticed that there is a difference
when running with/without the patch though - when running with the patch, the
protobuf jar is second on the classpath, whereas when running without the patch
it's far far away. So I've explored all jars on the classpath before the
protobuf one when running without the patch and found out that hive (jar
hive-exec) contains all Hive's dependencies including protobuf that Hive
depends on. As a result when running without the patch Hive version of protobuf
is used instead of the required version 2.5.0 and our tests are failing.
> Make Sqoop build aware of the protobuf library
> ----------------------------------------------
>
> Key: SQOOP-1198
> URL: https://issues.apache.org/jira/browse/SQOOP-1198
> Project: Sqoop
> Issue Type: Bug
> Affects Versions: 1.4.4
> Reporter: Jarek Jarcec Cecho
> Assignee: Jarek Jarcec Cecho
> Fix For: 1.4.5
>
> Attachments: SQOOP-1198.patch
>
>
> Currently Sqoop build is using protobuf from local machine. As different
> Hadoop versions are using different protobuf versions, I would suggest to
> make the build aware of the version and pull in version that is required.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
