Github user jkbradley commented on the issue:
https://github.com/apache/spark/pull/17336
Thanks for this PR! Do you think it's worth adding the caching logic? I'm
now wondering if we should change associationRules into a method which
recomputes the DataFrame every time it is called. That will make it easier for
the user to understand the semantics, and it would be easy for a user to define
a val to hold onto the computed DataFrame if needed.
Would you mind updating this accordingly? Thanks!
---
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
