Hi Moon,
I am using Spark/Scala code as below
import java.util.Calendar
import org.joda.time._
val option = z.input("option","2").toString.toInt
val today = new DateTime()
val minutes = -15
val minutesago =
today.plusMinutes(minutes).toString.toString.substring(11,19)
val date = java.time.LocalD
Hi,
Thanks for sharing problem.
If you're using Scala in SparkInterpreter, Scala REPL may have some problem
[1] when there is a lot of calls.
If you're using only SparkSQL or other interpreter, but still experience
the same, then it is Zeppelin's own problem.
Could you share little more informa
Hi,
I have been testing Zeppelin in conjunction with Spark sql and Spark
functional programming. I notice that as time gets by and many calls are
made with the same session open with different codes and plots, Zeppelin
becomes very slow and eventually one gets a message "pipe broken" in the
run.
