Skip to content

[Data] Make _hash_partition a separate function#55759

Merged
alexeykudinkin merged 1 commit intoray-project:masterfrom
goutamvenkat-anyscale:goutam/hash_partition_merge_conflict
Aug 20, 2025
Merged

[Data] Make _hash_partition a separate function#55759
alexeykudinkin merged 1 commit intoray-project:masterfrom
goutamvenkat-anyscale:goutam/hash_partition_merge_conflict

Conversation

@goutamvenkat-anyscale
Copy link
Copy Markdown
Contributor

Why are these changes needed?

A tiny clean up, make the hash partitioning phase a separate function for readability.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • I've included any doc changes needed for https://docs.ray.io/en/master/.
    • I've added any new APIs to the API Reference. For example, if I added a
      method in Tune, I've added it in doc/source/tune/api/ under the
      corresponding .rst file.
  • I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
  • Testing Strategy
    • Unit tests
    • Release tests
    • This PR is not tested :(

Signed-off-by: Goutam V <goutam@anyscale.com>
@goutamvenkat-anyscale goutamvenkat-anyscale requested a review from a team as a code owner August 19, 2025 23:30
@goutamvenkat-anyscale goutamvenkat-anyscale added the data Ray Data-related issues label Aug 19, 2025
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request refactors the hash partitioning logic into a separate _hash_partition function for better readability and maintainability. The change is clean and improves the code. I have one minor suggestion to remove a misleading comment from the newly created function.

@goutamvenkat-anyscale goutamvenkat-anyscale added the go add ONLY when ready to merge, run all tests label Aug 20, 2025
@alexeykudinkin alexeykudinkin merged commit 359d241 into ray-project:master Aug 20, 2025
5 checks passed
dioptre pushed a commit to sourcetable/ray that referenced this pull request Aug 20, 2025
Signed-off-by: Andrew Grosser <dioptre@gmail.com>
alimaazamat pushed a commit to alimaazamat/ray that referenced this pull request Aug 21, 2025
jugalshah291 pushed a commit to jugalshah291/ray_fork that referenced this pull request Sep 11, 2025
Signed-off-by: jugalshah291 <shah.jugal291@gmail.com>
dstrodtman pushed a commit that referenced this pull request Oct 6, 2025
Signed-off-by: Douglas Strodtman <douglas@anyscale.com>
landscapepainter pushed a commit to landscapepainter/ray that referenced this pull request Nov 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

data Ray Data-related issues go add ONLY when ready to merge, run all tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants