[data] Integrate Ray Dataset with Daft Dataframe #51531
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
8 tasks
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
jaychia
force-pushed
the
jay/daft-integration
branch
from
9294f0d to
c15529f
Compare
richardliaw
approved these changes
Mar 19, 2025
Signed-off-by: Jay Chia <[email protected]>
jaychia
force-pushed
the
jay/daft-integration
branch
from
3b1faf4 to
28e519f
Compare
Signed-off-by: Jay Chia <[email protected]>
Signed-off-by: Jay Chia <[email protected]>
jaychia
force-pushed
the
jay/daft-integration
branch
from
c973a14 to
a19970e
Compare
Signed-off-by: Jay Chia <[email protected]>
jaychia
force-pushed
the
jay/daft-integration
branch
from
506a7be to
1d8c7ac
Compare
Signed-off-by: Richard Liaw <[email protected]>
dhakshin32
pushed a commit
to dhakshin32/ray
that referenced
this pull request
Mar 27, 2025
<!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? This adds nice integrations between Daft and Ray Data along with: Unit test for data round-trip (including more interesting types such as a Tensor) Documentation Implementation on Ray Dataset for conversion to/from Daft Dataframes ## Related issue number Re-opening ray-project#50630 which was borked by a bad rebase. ## Checks - [x] 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. - [x] I've included any doc changes needed for https://docs.ray.io/en/master/. - [x] 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. - [x] 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 - [x] Unit tests - [ ] Release tests - [ ] This PR is not tested :( --------- Signed-off-by: Jay Chia <[email protected]> Signed-off-by: Richard Liaw <[email protected]> Co-authored-by: Richard Liaw <[email protected]> Signed-off-by: Dhakshin Suriakannu <[email protected]>
srinathk10
pushed a commit
that referenced
this pull request
Mar 28, 2025
<!-- Thank you for your contribution! Please review https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before opening a pull request. --> <!-- Please add a reviewer to the assignee section when you create a PR. If you don't have the access to it, we will shortly find a reviewer and assign them to your PR. --> ## Why are these changes needed? This adds nice integrations between Daft and Ray Data along with: Unit test for data round-trip (including more interesting types such as a Tensor) Documentation Implementation on Ray Dataset for conversion to/from Daft Dataframes ## Related issue number Re-opening #50630 which was borked by a bad rebase. ## Checks - [x] 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. - [x] I've included any doc changes needed for https://docs.ray.io/en/master/. - [x] 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. - [x] 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 - [x] Unit tests - [ ] Release tests - [ ] This PR is not tested :( --------- Signed-off-by: Jay Chia <[email protected]> Signed-off-by: Richard Liaw <[email protected]> Co-authored-by: Richard Liaw <[email protected]> Signed-off-by: Srinath Krishnamachari <[email protected]>
8 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why are these changes needed?
This adds nice integrations between Daft and Ray Data along with:
Unit test for data round-trip (including more interesting types such as a Tensor)
Documentation
Implementation on Ray Dataset for conversion to/from Daft Dataframes
Related issue number
Re-opening #50630 which was borked by a bad rebase.
Checks
git commit -s) in this PR.scripts/format.shto lint the changes in this PR.method in Tune, I've added it in
doc/source/tune/api/under thecorresponding
.rstfile.