Thanks for the link. Yeah if there's no need to copy execution.id from parent
to child then I agree, you could strip it out, presumably in this part of
the code using some kind of configuration as to which properties shouldn't
go across
SparkContext:
protected[spark] val localProperties = new
InheritableThreadLocal[Properties] {
override protected def childValue(parent: Properties): Properties = {
// Note: make a clone such that changes in the parent properties
aren't reflected in
// the those of the children threads, which has confusing semantics
(SPARK-10563).
SerializationUtils.clone(parent).asInstanceOf[Properties]
}
override protected def initialValue(): Properties = new Properties()
}
--
View this message in context:
http://apache-spark-developers-list.1001551.n3.nabble.com/IllegalArgumentException-spark-sql-execution-id-is-already-set-tp19124p19190.html
Sent from the Apache Spark Developers List mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe e-mail: dev-unsubscr...@spark.apache.org
