[
https://issues.apache.org/jira/browse/HBASE-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14058839#comment-14058839
]
Nick Dimiduk commented on HBASE-11118:
--------------------------------------
[~fs111] I pulled cascading.hbase and did a {{gradle clean build}}. I think the
reason you're seeing compat.module issues is because this project has
dependencies against hbase/hadoop1 and I only pushed hadoop2 artifacts.
{noformat}
:check UP-TO-DATE
:build
:cascading-hbase-hadoop:compileJava
Download
http://repo1.maven.org/maven2/org/apache/hbase/hbase-client/0.98.1-hadoop1/hbase-client-0.98.1-hadoop1.pom
Download
http://repo1.maven.org/maven2/org/apache/hbase/hbase/0.98.1-hadoop1/hbase-0.98.1-hadoop1.pom
Download
http://repo1.maven.org/maven2/org/apache/hbase/hbase-server/0.98.1-hadoop1/hbase-server-0.98.1-hadoop1.pom
Download
http://repo1.maven.org/maven2/org/apache/hbase/hbase-common/0.98.1-hadoop1/hbase-common-0.98.1-hadoop1.pom
Download
http://repo1.maven.org/maven2/org/apache/hbase/hbase-hadoop1-compat/0.98.1-hadoop1/hbase-hadoop1-compat-0.98.1-hadoop1.pom
...
{noformat}
Let me build both hadoop compat modules and give this a try.
> 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
> Affects Versions: 0.98.2
> Reporter: André Kelpe
> 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.patch.gz,
> HBASE-11118-trunk.patch.gz, HBASE-11118.00.patch, HBASE-11118.01.patch,
> HBASE-11118.02.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)
