Github user hvanhovell commented on the issue:
https://github.com/apache/spark/pull/16575
I suppose it makes sense. The only thing I am wondering if this doesn't
subtly breaks things. I am certain that some weirdness is to be expected with
respect to session local configurations. For instance the plan could be
analyzed under one set of configurations and be executed under a different set.
I do think that we should consistent.
@robert3005 could you revert all the caching logic which is currently part
of this PR, and just make this about SparkSessions?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
