[SPARK-58606][ML] Move association-rule collection and preparation in FPGrowthModel transform from driver to executors - #57806
Closed
zhengruifeng wants to merge 8 commits into
Closed
Conversation
zhengruifeng
changed the title
zhengruifeng
changed the title
zhengruifeng
changed the title
HyukjinKwon
approved these changes
Aug 6, 2026
zhengruifeng
added a commit
that referenced
this pull request
Aug 6, 2026
… FPGrowthModel transform from driver to executors ### What changes were proposed in this pull request? This PR replaces the manually collected association-rule array and user-defined function in `FPGrowthModel.transform` with DataFrame operations. It joins input transactions with matching rules, aggregates consequents for each input row, and uses `array_except` to exclude items already present in the transaction. The join has no broadcast hint, so Catalyst may use a broadcast nested-loop join only when the plan statistics consider a side small enough. ### Why are the changes needed? Collecting every association rule before a transform creates avoidable driver-memory pressure, particularly for Spark Connect server workloads with many rules. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? - `build/sbt -java-home /usr/lib/jvm/java-17-openjdk-amd64 mllib/compile` - The focused `FPGrowthSuite` has not been run locally yet. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-5) Closes #57806 from zhengruifeng/ml_fpgrowth_transform_join. Authored-by: Ruifeng Zheng <ruifengz@apache.org> Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com> (cherry picked from commit 21a1ae1) Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
Contributor
Author
zhengruifeng
added a commit
that referenced
this pull request
Aug 6, 2026
### What changes were proposed in this pull request? This follow-up to #57806 gives the transient association-rules column in `FPGrowthModel.transform` a generated name instead of the fixed name `rules`. It also adds regression coverage for an input dataset that already contains a `rules` column. ### Why are the changes needed? The fixed temporary column can conflict with an input column of the same name after the join, causing ambiguous-column analysis failures or dropping the user's column. ### Does this PR introduce _any_ user-facing change? Yes. `FPGrowthModel.transform` now supports and preserves an input column named `rules`. ### How was this patch tested? - `build/sbt -java-home /usr/lib/jvm/java-17-openjdk-amd64 mllib/Test/compile` - Added `FPGrowthSuite` coverage for an input `rules` column. The focused suite has not been run locally yet. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-5) Closes #57816 from zhengruifeng/ml_fpgrowth_temp_rules_column. Authored-by: Ruifeng Zheng <ruifengz@apache.org> Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
zhengruifeng
added a commit
that referenced
this pull request
Aug 6, 2026
### What changes were proposed in this pull request? This follow-up to #57806 gives the transient association-rules column in `FPGrowthModel.transform` a generated name instead of the fixed name `rules`. It also adds regression coverage for an input dataset that already contains a `rules` column. ### Why are the changes needed? The fixed temporary column can conflict with an input column of the same name after the join, causing ambiguous-column analysis failures or dropping the user's column. ### Does this PR introduce _any_ user-facing change? Yes. `FPGrowthModel.transform` now supports and preserves an input column named `rules`. ### How was this patch tested? - `build/sbt -java-home /usr/lib/jvm/java-17-openjdk-amd64 mllib/Test/compile` - Added `FPGrowthSuite` coverage for an input `rules` column. The focused suite has not been run locally yet. ### Was this patch authored or co-authored using generative AI tooling? Generated-by: Codex (GPT-5) Closes #57816 from zhengruifeng/ml_fpgrowth_temp_rules_column. Authored-by: Ruifeng Zheng <ruifengz@apache.org> Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com> (cherry picked from commit 5aeb251) Signed-off-by: Ruifeng Zheng <ruifengz@foxmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
This PR replaces the manually collected association-rule array and user-defined function in
FPGrowthModel.transformwith DataFrame operations. It joins input transactions with matching rules, aggregates consequents for each input row, and usesarray_exceptto exclude items already present in the transaction.The join has no broadcast hint, so Catalyst may use a broadcast nested-loop join only when the plan statistics consider a side small enough.
Why are the changes needed?
Collecting every association rule before a transform creates avoidable driver-memory pressure, particularly for Spark Connect server workloads with many rules.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
build/sbt -java-home /usr/lib/jvm/java-17-openjdk-amd64 mllib/compileFPGrowthSuitehas not been run locally yet.Was this patch authored or co-authored using generative AI tooling?
Generated-by: Codex (GPT-5)