hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From André Kelpe (JIRA) <j...@apache.org>
Subject [jira] [Commented] (HBASE-11118) non environment variable solution for "IllegalAccessError: class com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass com.google.protobuf.LiteralByteString"
Date Thu, 19 Jun 2014 12:57:26 GMT

    [ https://issues.apache.org/jira/browse/HBASE-11118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14037318#comment-14037318
] 

André Kelpe commented on HBASE-11118:
-------------------------------------

[~stack] : We do have the hbase-server deps in the jars. This is due to the fact that we are
based on a fork of the mapred InputFormat/OutputFormat, which uses the TableSplit class to
calculate the InputSplits. The problem is that we cannot use the mapreduce apis in cascading
and our version of the Input and OutputFormat has evolved and we want to keep it for backwards
compatibility.


If there is a way to get this working w/o the hbase-server deps, I am more than happy to drop
it. The code is here, if that helps: https://github.com/Cascading/cascading.hbase

> 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
>
>         Attachments: 1118.suggested.undoing.optimization.on.clientside.txt, 1118.suggested.undoing.optimization.on.clientside.txt,
HBASE-11118-0.98.patch.gz, HBASE-11118-trunk.patch.gz, 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)

Mime
View raw message