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-49540][PS] Unify the usage of distributed_sequence_id #48028

Closed

Conversation

zhengruifeng
Copy link
Contributor

What changes were proposed in this pull request?

in PySpark Classic, it was used via a dataframe method withSequenceColumn, while in PySpark Connect, it was used as an internal function

This PR unifies the usage of distributed_sequence_id

Why are the changes needed?

code refactoring

Does this PR introduce any user-facing change?

No

How was this patch tested?

updated tests

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

No

@itholic
Copy link
Contributor

itholic commented Sep 9, 2024

Nice cleanup

@zhengruifeng
Copy link
Contributor Author

thanks, merged to master

@zhengruifeng zhengruifeng deleted the func_withSequenceColumn branch September 9, 2024 04:26
IvanK-db pushed a commit to IvanK-db/spark that referenced this pull request Sep 20, 2024
### What changes were proposed in this pull request?

in PySpark Classic, it was used via a dataframe method `withSequenceColumn`, while in PySpark Connect, it was used as an internal function

This PR unifies the usage of `distributed_sequence_id`

### Why are the changes needed?
code refactoring

### Does this PR introduce _any_ user-facing change?
No

### How was this patch tested?
updated tests

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

Closes apache#48028 from zhengruifeng/func_withSequenceColumn.

Authored-by: Ruifeng Zheng <ruifengz@apache.org>
Signed-off-by: Ruifeng Zheng <ruifengz@apache.org>
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.

4 participants