On 16 May 2015, at 04:39, Anton Brazhnyk
mailto:anton.brazh...@genesys.com>> wrote:
For me it wouldn’t help I guess, because those newer classes would still be
loaded by different classloader.
What did work for me with 1.3.1 – removing of those classes from Spark’s jar
completely, so they get
x27;s Guava pieces cause exceptions in non-trivial deployments
Ah, I see. yeah, it sucks that Spark has to expose Optional (and things it
depends on), but removing that would break the public API, so...
One last thing you could try is do add your newer Guava jar to
"spark.driver.extraClas
#x27;s suggestion of shading Guava in your app
>>>> can be used as a last resort.
>>>>
>>>>
>>>> On Thu, May 14, 2015 at 7:38 PM, Anton Brazhnyk <
>>>> anton.brazh...@genesys.com> wrote:
>>>>
>>>>> The pr
t;>
>>>> The problem is with 1.3.1
>>>>
>>>> It has Function class (mentioned in exception) in
>>>> spark-network-common_2.10-1.3.1.jar.
>>>>
>>>> Our current resolution is actually backport to 1.2.2, which is working
>>>>
n class (mentioned in exception) in
>>> spark-network-common_2.10-1.3.1.jar.
>>>
>>> Our current resolution is actually backport to 1.2.2, which is working
>>> fine.
>>>
>>>
>>>
>>>
>>>
>>> *From:* Marcelo Vanz
on) in
>> spark-network-common_2.10-1.3.1.jar.
>>
>> Our current resolution is actually backport to 1.2.2, which is working
>> fine.
>>
>>
>>
>>
>>
>> *From:* Marcelo Vanzin [mailto:van...@cloudera.com]
>> *Sent:* Thursday, May 14, 2015 6
resolution is actually backport to 1.2.2, which is working
> fine.
>
>
>
>
>
> *From:* Marcelo Vanzin [mailto:van...@cloudera.com]
> *Sent:* Thursday, May 14, 2015 6:27 PM
> *To:* Anton Brazhnyk
> *Cc:* user@spark.apache.org
> *Subject:* Re: Spark's Guava pieces ca
is actually backport to 1.2.2, which is working
> fine.
>
>
>
>
>
> *From:* Marcelo Vanzin [mailto:van...@cloudera.com]
> *Sent:* Thursday, May 14, 2015 6:27 PM
> *To:* Anton Brazhnyk
> *Cc:* user@spark.apache.org
> *Subject:* Re: Spark's Guava pieces cause ex
Cc: user@spark.apache.org
Subject: Re: Spark's Guava pieces cause exceptions in non-trivial deployments
What version of Spark are you using?
The bug you mention is only about the Optional class (and a handful of others,
but none of the classes you're having problems with). All other Gua
What version of Spark are you using?
The bug you mention is only about the Optional class (and a handful of
others, but none of the classes you're having problems with). All other
Guava classes should be shaded since Spark 1.2, so you should be able to
use your own version of Guava with no problem
Greetings,
I have a relatively complex application with Spark, Jetty and Guava (16) not
fitting together.
Exception happens when some components try to use "mix" of Guava classes
(including Spark's pieces) that are loaded by different classloaders:
java.lang.LinkageError: loader constraint viola
11 matches
Mail list logo