feat: Added RemoteDatasetProxy that executes Ray Data operations remotely#5637
Merged
ntkathole merged 1 commit intofeast-dev:masterfrom Sep 26, 2025
Merged
Conversation
d1bb103 to
a481f1c
Compare
franciscojavierarceo
approved these changes
Sep 26, 2025
Member
franciscojavierarceo
left a comment
There was a problem hiding this comment.
This is fine, the syntax of is_ray_dataset instead of is instance is ugly though
a481f1c to
193c893
Compare
Member
Author
Tried to make it little better with |
…tely Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
193c893 to
3322130
Compare
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
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.
What this PR does / why we need it:
This PR adds support to run Ray Datasets operations on remote Kuberay cluster. Implemented
RemoteDatasetProxyclass, that wraps all Ray Dataset operations in@ray.remotefunctions, ensuring they execute on KubeRay cluster workers.Which issue(s) this PR fixes:
#5633