Github user hhbyyh commented on the issue:
https://github.com/apache/spark/pull/15415
@jkbradley Sent an update to refine the transform code and address the
comments.
Regarding to the behavior changing concern, I think different partition
strategy will only affect the overall efficiency and maybe the order of the
frequent itemsets and association rules. As long as the result set does not
change, I don't think it will disturb the users. Let me know if I miss
anything.
---
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
