Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Mon, 16 Jun 2014 13:42:03 +0000 (UTC)
From: =?utf-8?Q?Andr=C3=A9_Kelpe_=28JIRA=29?= <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12712613.1399392555581.137378.1402926123561@arcas>
In-Reply-To: <JIRA.12712613.1399392555581@arcas>
References: <JIRA.12712613.1399392555581@arcas>
Subject: [jira] [Commented] (HBASE-11118) non environment variable solution
 for "IllegalAccessError: class
 com.google.protobuf.ZeroCopyLiteralByteString cannot access its superclass
 com.google.protobuf.LiteralByteString"
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HBASE-11118?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D140=
32427#comment-14032427 ]=20

Andr=C3=A9 Kelpe commented on HBASE-11118:
-------------------------------------

[~todd@lipcon.org] Cascading uses the JobClient to submit the jobs on the f=
ly, but we don't call the hadoop shell wrapper for each job, like hive does=
. All submission is handled internally. The initial program gets started wi=
th hadoop/yarn jar myJar, and then we handle everything ourselves. In the l=
ingual case, it is even more complicated, since we fetch jars dynamically a=
t runtime and add them to the classpath of the jobs, which means we cannot =
know upfront, if the job is going to use cascading-hbase or not.

> non environment variable solution for "IllegalAccessError: class com.goog=
le.protobuf.ZeroCopyLiteralByteString cannot access its superclass com.goog=
le.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=C3=A9 Kelpe
>            Priority: Blocker
>             Fix For: 0.99.0, 0.98.4
>
>         Attachments: HBASE-11118-0.98.patch.gz, HBASE-11118-trunk.patch.g=
z, 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.h=
base (https://github.com/cascading/cascading.hbase).
> One of the features of cascading.hbase is that you can use it from lingua=
l (http://www.cascading.org/projects/lingual/), our SQL layer for hadoop. l=
ingual has a notion of providers, which are fat jars that we pull down dyna=
mically at runtime. Those jars give users the ability to talk to any system=
 or format from SQL. They are added to the classpath  programmatically befo=
re we submit jobs to a hadoop cluster.
> Since lingual does not know upfront , which providers are going to be use=
d 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 r=
equires this right now.
> It would be great to have a programmatical way to fix this, when using fa=
t jars.


--
This message was sent by Atlassian JIRA
(v6.2#6252)