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

[Data] Mark num_rows_per_file as experimental #48208

Merged
merged 1 commit into from
Oct 23, 2024
Merged

Conversation

bveeramani
Copy link
Member

Why are these changes needed?

num_rows_per_file has known issues. In specific:

  • If the number of rows per block is larger than the specified value, then Ray Data writes the number of rows per block to each file.
  • If specified value isn't divisible by the number of rows per block, then Ray Data writes fewer than the specified value (i.e., the remainder) to some files.
  • Writes aren't streamed (in the sense that all blocks for that write are stored in heap memory at the same time), so this feature is prone to OOMing

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: Balaji Veeramani <bveeramani@berkeley.edu>
@bveeramani bveeramani enabled auto-merge (squash) October 23, 2024 18:26
@github-actions github-actions bot added the go add ONLY when ready to merge, run all tests label Oct 23, 2024
@bveeramani bveeramani merged commit 56d8ec9 into master Oct 23, 2024
6 checks passed
@bveeramani bveeramani deleted the num-rows-per-file-doc branch October 23, 2024 19:28
Jay-ju pushed a commit to Jay-ju/ray that referenced this pull request Nov 5, 2024
If you don't have the access to it, we will shortly find a reviewer and
num_rows_per_file has known issues. In specific:

- If the number of rows per block is larger than the specified value, then Ray Data writes the number of rows per block to each file.
- If specified value isn't divisible by the number of rows per block, then Ray Data writes fewer than the specified value (i.e., the remainder) to some files.
- Writes aren't streamed (in the sense that all blocks for that write are stored in heap memory at the same time), so this feature is prone to OOMing

Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
JP-sDEV pushed a commit to JP-sDEV/ray that referenced this pull request Nov 14, 2024
If you don't have the access to it, we will shortly find a reviewer and
num_rows_per_file has known issues. In specific:

- If the number of rows per block is larger than the specified value, then Ray Data writes the number of rows per block to each file.
- If specified value isn't divisible by the number of rows per block, then Ray Data writes fewer than the specified value (i.e., the remainder) to some files.
- Writes aren't streamed (in the sense that all blocks for that write are stored in heap memory at the same time), so this feature is prone to OOMing

Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
mohitjain2504 pushed a commit to mohitjain2504/ray that referenced this pull request Nov 15, 2024
If you don't have the access to it, we will shortly find a reviewer and
num_rows_per_file has known issues. In specific:

- If the number of rows per block is larger than the specified value, then Ray Data writes the number of rows per block to each file.
- If specified value isn't divisible by the number of rows per block, then Ray Data writes fewer than the specified value (i.e., the remainder) to some files.
- Writes aren't streamed (in the sense that all blocks for that write are stored in heap memory at the same time), so this feature is prone to OOMing

Signed-off-by: Balaji Veeramani <bveeramani@berkeley.edu>
Signed-off-by: mohitjain2504 <mohit.jain@dream11.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
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