Github user chenghao-intel commented on the pull request:
https://github.com/apache/spark/pull/5714#issuecomment-107271454
Ok, I got your mean, creating its own query execution for `Cachemanager` is
a good idea,
but probably still has bug; Consider cases like (It's probably quite rare
case, but possible from user code):
```scala
val rdd = mydf.javaToPython // queryExecution.executedPlan will be called.
mydf.cache()
mydf.collect() // will not be benefit from the cache
```
---
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]
