[
https://issues.apache.org/jira/browse/TOREE-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15147960#comment-15147960
]
Chip Senkbeil commented on TOREE-250:
-------------------------------------
This was related to Spark, so if it went away with a later version of spark,
close it.
> spark.sql.execution.id is already set
> -------------------------------------
>
> Key: TOREE-250
> URL: https://issues.apache.org/jira/browse/TOREE-250
> Project: TOREE
> Issue Type: Bug
> Affects Versions: NOV_2015, DEC_2015, JAN_2016
> Environment: toree-kernel-0.1.0-SNAPSHOT
> Spark 1.5.2 built for Hadoop 2.6.0
> Reporter: George Lucchese
> Priority: Minor
> Labels: newbie
>
> When using the SQL Magic, on occasion this exception is thrown:
> ```
> java.lang.IllegalArgumentException: spark.sql.execution.id is already set
> at
> org.apache.spark.sql.execution.SQLExecution$.withNewExecutionId(SQLExecution.scala:87)
> at
> org.apache.spark.sql.DataFrame.withNewExecutionId(DataFrame.scala:1903)
> at org.apache.spark.sql.DataFrame.collect(DataFrame.scala:1384)
> at org.apache.spark.sql.DataFrame.head(DataFrame.scala:1314)
> at org.apache.spark.sql.DataFrame.take(DataFrame.scala:1377)
> at org.apache.spark.sql.DataFrame.showString(DataFrame.scala:178)
> at org.apache.spark.sql.DataFrame.show(DataFrame.scala:401)
> at org.apache.spark.sql.DataFrame.show(DataFrame.scala:362)
> at
> org.apache.toree.kernel.interpreter.sql.SqlService$$anonfun$submitCode$1$$anonfun$1.apply$mcV$sp(SqlService.scala:58)
> at
> org.apache.toree.kernel.interpreter.sql.SqlService$$anonfun$submitCode$1$$anonfun$1.apply(SqlService.scala:58)
> at
> org.apache.toree.kernel.interpreter.sql.SqlService$$anonfun$submitCode$1$$anonfun$1.apply(SqlService.scala:58)
> at scala.util.DynamicVariable.withValue(DynamicVariable.scala:57)
> at scala.Console$.withOut(Console.scala:126)
> at
> org.apache.toree.kernel.interpreter.sql.SqlService$$anonfun$submitCode$1.apply(SqlService.scala:56)
> at
> org.apache.toree.kernel.interpreter.sql.SqlService$$anonfun$submitCode$1.apply(SqlService.scala:48)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.liftedTree1$1(Future.scala:24)
> at
> scala.concurrent.impl.Future$PromiseCompletingRunnable.run(Future.scala:24)
> at
> scala.concurrent.impl.ExecutionContextImpl$$anon$3.exec(ExecutionContextImpl.scala:107)
> at
> scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)
> at
> scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)
> at
> scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)
> at
> scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)
> ```
> This seems to only affect the SQL interpreter. A scala interpreter can still
> execute SQL queries in the same kernel instance. The only resolution at
> runtime is to restart the whole kernel.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
