Github user nchammas commented on the issue:
https://github.com/apache/spark/pull/14579
Ah, you're right.
So if we want to avoid needing magic methods in the main RDD/DataFrame
classes and avoid needing a separate utility method like `cache()`, I think one
option available to us is to have separate `PersistedRDD` and
`PersistedDataFrame` classes that simply wrap the base RDD and DataFrames
classes and add the appropriate magic methods.
`.persist()` and `.cache()` would then return instances of these classes,
which should satisfy the `type(x).__enter__(x)` behavior while still preserving
backwards compatibility and method chaining.
What do you think of that?
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
