[
https://issues.apache.org/jira/browse/HBASE-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14184296#comment-14184296
]
Arijit Banerjee commented on HBASE-11118:
-----------------------------------------
Thanks Nick for the quick response. We are using CDH5.1.0 with HBase 0.98.1. It
seems from HBASE-11118 that this issue is fixed as of hbase 0.98.4 . Our
application works fine when submitting directly from commandline after setting
the following environment variable but it fails when spawned via Oozie. We have
set the env variable in all data nodes, hadoop-env.sh for all users but without
luck(probably being overridden somewhere). Wondering if there is any workaround
for 0.98.1 with Oozie 4.0.
export
HADOOP_CLASSPATH=/usr/share/cmf/lib/cdh5/hbase-protocol-0.98.1-cdh5.1.0.jar:/etc/hbase/conf
> 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.3.4#6332)
