Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SPARK-50898][ML][PYTHON][CONNECT] Support FPGrowth on connect #49579

Closed
wants to merge 2 commits into from

Conversation

zhengruifeng
Copy link
Contributor

What changes were proposed in this pull request?

Support FPGrowth on connect

Why are the changes needed?

for feature parity

Does this PR introduce any user-facing change?

Yes, new algorithms supported on connect

How was this patch tested?

added tests

Was this patch authored or co-authored using generative AI tooling?

No

@zhengruifeng
Copy link
Contributor Author

cc @wbo4958

Copy link
Contributor

@wbo4958 wbo4958 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

zhengruifeng added a commit that referenced this pull request Jan 21, 2025
### What changes were proposed in this pull request?
Support `FPGrowth` on connect

### Why are the changes needed?
for feature parity

### Does this PR introduce _any_ user-facing change?
Yes, new algorithms supported on connect

### How was this patch tested?
added tests

### Was this patch authored or co-authored using generative AI tooling?
No

Closes #49579 from zhengruifeng/ml_connect_fpm.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@apache.org>
(cherry picked from commit 3ba74bf)
Signed-off-by: Ruifeng Zheng <ruifengz@apache.org>
@zhengruifeng
Copy link
Contributor Author

thanks, merged to master/4.0

@zhengruifeng zhengruifeng deleted the ml_connect_fpm branch January 21, 2025 08:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants