Cangatulations Apache Zeppelin community.
I am sure our users will appreciate your efforts and this release.
Let's make Zeppelin great.
On Tue, Jun 13, 2017 at 10:08 AM Jun Kim wrote:
> Cool! Thanks for your work Mina :)
>
> 2017년 6월 14일 (수) 오전 2:06, Mina Lee 님이 작성:
>
>> The Apache Zeppelin c
Hi Richard,
Is it possible for you to upgrade to 0.6.2 to 0.7.1 ?
0.6.0 has some critical issue
Richard Xin 于2017年6月15日周四 上午5:02写道：
> and I also saw stack overflow issue:
> Caused by: java.lang.StackOverflowError
> at
> scala.tools.nsc.transform.LambdaLift$$anon$1.apply(LambdaLift.scala:3
and I also saw stack overflow issue:Caused by: java.lang.StackOverflowError
at scala.tools.nsc.transform.LambdaLift$$anon$1.apply(LambdaLift.scala:30)
at scala.reflect.internal.tpe.TypeMaps$TypeMap.mapOver(TypeMaps.scala:110)
at scala.tools.nsc.transform.LambdaLift$$anon$1.apply(LambdaL
it happened several times already, worked again after restart Zeppelin
I see consistently similar error when died
ERROR [2017-06-14 17:59:59,705] ({pool-2-thread-2}
SparkInterpreter.java[putLatestVarInResourcePool]:1253) -
java.lang.NullPointerException
at scala.tools.nsc.interpreter.IMain$Rea
>>> But not sure about how other interpreters can do the same thing. (e.g
trivial, but let’s think about shell interpreter which keeps it’s tabledata
on memory)
The approach I proposed is general for all the interpreters. What we need
do is to add one method in RemoteInterpreterProcess for other
i
I believe it's a good idea to select which interpreters to keep in the
"default release", should we track this through JIRA?
2017-06-11 17:05 GMT+02:00 Jongyoul Lee :
> Thanks, Alex.
>
> I left comments we started to discuss on it recently.
>
> On Sun, Jun 11, 2017 at 6:50 PM, Alexander Bezzubov
