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] Add concurrency for write APIs #43177

Merged
merged 1 commit into from
Feb 15, 2024

Conversation

c21
Copy link
Contributor

@c21 c21 commented Feb 14, 2024

Why are these changes needed?

This PR is to add concurrency parameter to write APIs. This makes write to be consistent with read and map-like APIs. So users can control concurrency through read-map-write workflow.

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: Cheng Su <scnju13@gmail.com>
@raulchen raulchen merged commit 638f77f into ray-project:master Feb 15, 2024
9 checks passed
@c21 c21 deleted the write-concurrency branch February 15, 2024 23:43
kevin85421 pushed a commit to kevin85421/ray that referenced this pull request Feb 17, 2024
This PR is to add concurrency parameter to write APIs. This makes write to be consistent with read and map-like APIs. So users can control concurrency through read-map-write workflow.

Signed-off-by: Cheng Su <scnju13@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants