Github user liancheng commented on the pull request:
https://github.com/apache/spark/pull/4382#issuecomment-76901265
@chenghao-intel I'm posting the summary of our offline discussion here for
future reference:
`SQLContext.CacheManager` maps to `SparkContext.CacheManager` in a
one-to-one manner. Once the SQL cache manager is made a global object, users
can only use a single `SparkContext` in a single process. This limitation is
neither wanted nor necessary. On the other hand, moving session specific stuff
to `SQLSession` and leaving stuff shared by multiple sessions in
`SQLContext`/`HiveContext` avoids this problem.
---
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]
