fix: Fix Ray source materialization for KubeRay on Kubernetes#6407
Merged
Conversation
2871aea to
3303ed8
Compare
franciscojavierarceo
approved these changes
May 15, 2026
Signed-off-by: ntkathole <nikhilkathole2683@gmail.com>
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:
When using RaySource with BatchFeatureView in a KubeRay-managed cluster on Kubernetes, materialization fails with multiple issues:
kuberay_confeven for in-cluster pods that authenticate via service accounts, making deployment on managed Kubernetes platforms impossible without manual token injection.runtime_envcannot be passed to the Ray client connection, so additional pip dependencies (e.g. datasets, sentence-transformers) needed by Ray workers cannot be specified via configuration — they must be baked into every worker image.from_huggingface()withAttributeError: 'Dataset' object has no attribute 'to_arrow'. HF Dataset objects are backed by memory-mapped .arrow files which cannot be deserialized on remote Ray workers across the network.feast[ray]extras, requiring users to manually install it despite RaySource depending on it.