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
Inh
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
Hi,
We've received the following error a handful of times and once it's occurred
all subsequent queries fail with the same exception until we bounce the
instance:
IllegalArgumentException: spark.sql.execution.id is already set
at
org.apache.spark.sql.execution.SQLExecution$.withNewExecuti