Hi Reynold,
I had version 2.6.1 in my project which was provided by the fine folks
from spring-boot-dependencies.
Now have overridden it to 2.7.8 :)
Sjoerd
2015-11-01 8:22 GMT+01:00 Reynold Xin :
> Thanks for reporting it, Sjoerd. You might have a different version of
> Janino brought in from
Thanks for reporting it, Sjoerd. You might have a different version of
Janino brought in from somewhere else.
This should fix your problem: https://github.com/apache/spark/pull/9372
Can you give it a try?
On Tue, Oct 27, 2015 at 9:12 PM, Sjoerd Mulder
wrote:
> No the job actually doesn't fai
No the job actually doesn't fail, but since our tests is generating all
these stacktraces i have disabled the tungsten mode just to be sure (and
don't have gazilion stacktraces in production).
2015-10-27 20:59 GMT+01:00 Josh Rosen :
> Hi Sjoerd,
>
> Did your job actually *fail* or did it just gen
Hi Sjoerd,
Did your job actually *fail* or did it just generate many spurious
exceptions? While the stacktrace that you posted does indicate a bug, I
don't think that it should have stopped query execution because Spark
should have fallen back to an interpreted code path (note the "Failed to
gener
I have disabled it because of it started generating ERROR's when upgrading
from Spark 1.4 to 1.5.1
2015-10-27T20:50:11.574+0100 ERROR TungstenSort.newOrdering() - Failed to
generate ordering, fallback to interpreted
java.util.concurrent.ExecutionException: java.lang.Exception: failed to
compile: o
Can you reply to this email and provide us with reasons why you disable it?
Thanks.
