Yeah that would work although I was worried that they used InheritableThreadLocal vs Threadlocal because they did want the child threads to inherit the parent's executionId, maybe to stop the child threads from kicking off their own queries whilst working for the parent. I think the fix would be to somehow ensure the child's execution.id was cleared when the parents is.
-- View this message in context: http://apache-spark-developers-list.1001551.n3.nabble.com/IllegalArgumentException-spark-sql-execution-id-is-already-set-tp19124p19145.html Sent from the Apache Spark Developers List mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
