You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Tony Reix (JIRA)" <ji...@apache.org> on 2014/11/04 13:00:42 UTC
[jira] [Commented] (AVRO-1567) Avro java tools tests fail with IBM
JVM
[ https://issues.apache.org/jira/browse/AVRO-1567?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14196031#comment-14196031 ]
Tony Reix commented on AVRO-1567:
---------------------------------
What's new about this issue ?
I've seen that some changes were made in 18.0-Snapshot.
> Avro java tools tests fail with IBM JVM
> ---------------------------------------
>
> Key: AVRO-1567
> URL: https://issues.apache.org/jira/browse/AVRO-1567
> Project: Avro
> Issue Type: Bug
> Components: java
> Affects Versions: 1.7.4, 1.7.7
> Environment: RHEL 6.5 on x86_64
> IBM JVM 7.1.1.1
> HADOOP 2.4.1
> Reporter: Tony Reix
> Priority: Blocker
> Original Estimate: 1h
> Remaining Estimate: 1h
>
> When using IBM JVM, compared to Oracle JVM, 25 of the Avro Tools tests fail.
> This is due to Avro using Hadoop which uses class:
> org/apache/hadoop/security/UserGroupInformation.java
> which makes use of:
> com.sun.security.auth.module.UnixLoginModule
> which does not exist in IBM JVM.
> Instead there is the class:
> com.ibm.security.auth.module.LinuxLoginModule
> that can be used in UserGroupInformation.java if the JVM is IBM.
> With a IBM-JVM patched version of Hadoop that takes care of the kind of JVM, these 25 Avro Java Tools tests still fail because the pom.xml file of:
> lang/java/tools/
> says unconditionnaly (starting line 146 in Avro 1.7.7) :
> <dependency>
> <groupId>org.apache.hadoop</groupId>
> <artifactId>hadoop-core</artifactId>
> Using:
> mvn -Phadoop2 -Dhadoop.version=2 test
> is of no help.
> In fact, hadoop-core exists only for old Hadoop versions (here version 0.20.205.0 is used by Avro), and not for Hadoop 2.4.1 .
> Replacing hadoop-core by hadoop-client in lang/java/tools/pom.xml file does fix the issue, as a work-around.
> However, a more rigorous solution is required, like it is done in lang/java/mapred/pom.xm , where hadoop-core is associated with hadoop1 and hadoop-client is associated with hadoop2 .
> I'm not an expert of Maven/pom.xml, and the pom.xml file of tools contains <exclusions> tags I have no idea. So, I'm not sure I can provide a correct patch.
> I guess that a Maven/pom.xml expert should be able to fix this in some minutes, plus testing.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)