[ https://issues.apache.org/jira/browse/HBASE-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14059842#comment-14059842 ]
Hudson commented on HBASE-11118: -------------------------------- FAILURE: Integrated in HBase-1.0 #32 (See [https://builds.apache.org/job/HBase-1.0/32/]) HBASE-11118 non environment variable solution for "IllegalAccessError: class com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass com.google.protobuf.LiteralByteString". -Addendum (anoopsamjohn: rev 15ba35b59330b408c76e18d9c8bb41329a11472b) * hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotManifestV1.java * hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/RSRpcServices.java * hbase-server/src/main/java/org/apache/hadoop/hbase/snapshot/SnapshotManifestV2.java * hbase-client/src/main/java/org/apache/hadoop/hbase/protobuf/ProtobufUtil.java > non environment variable solution for "IllegalAccessError: class > com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass > com.google.protobuf.LiteralByteString" > ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: HBASE-11118 > URL: https://issues.apache.org/jira/browse/HBASE-11118 > Project: HBase > Issue Type: Bug > Components: mapreduce > Affects Versions: 0.98.2 > Reporter: André Kelpe > Assignee: stack > Priority: Blocker > Fix For: 0.99.0, 0.98.4, 2.0.0 > > Attachments: 11118.098-0.txt, 11118.098.txt, 11118.bytestringer.txt, > 1118.suggested.undoing.optimization.on.clientside.txt, > 1118.suggested.undoing.optimization.on.clientside.txt, > HBASE-11118-0.98.00.patch, HBASE-11118-0.98.01.patch, > HBASE-11118-0.98.02.patch, HBASE-11118-0.98.03.patch, > HBASE-11118-0.98.patch.gz, HBASE-11118-trunk.patch.gz, HBASE-11118.00.patch, > HBASE-11118.01.patch, HBASE-11118.02.patch, HBASE-11118_0.98_addendum.patch, > HBASE-11118_master_addendum.patch, shade_attempt.patch > > > I am running into the problem described in > https://issues.apache.org/jira/browse/HBASE-10304, while trying to use a > newer version within cascading.hbase > (https://github.com/cascading/cascading.hbase). > One of the features of cascading.hbase is that you can use it from lingual > (http://www.cascading.org/projects/lingual/), our SQL layer for hadoop. > lingual has a notion of providers, which are fat jars that we pull down > dynamically at runtime. Those jars give users the ability to talk to any > system or format from SQL. They are added to the classpath programmatically > before we submit jobs to a hadoop cluster. > Since lingual does not know upfront , which providers are going to be used in > a given run, the HADOOP_CLASSPATH trick proposed in the JIRA above is really > clunky and breaks the ease of use we had before. No other provider requires > this right now. > It would be great to have a programmatical way to fix this, when using fat > jars. -- This message was sent by Atlassian JIRA (v6.2#6252)