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.

Sign up for GitHub

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

Jump to bottom

[Data] scheduling strategy of _sample_fragment task when reading parquet data #49099

Open
pfldy2850 opened this issue Dec 5, 2024 · 0 comments
Open

[Data] scheduling strategy of _sample_fragment task when reading parquet data #49099

pfldy2850 opened this issue Dec 5, 2024 · 0 comments
Labels
data Ray Data-related issues enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks

Comments

@pfldy2850
Copy link
Contributor

Description

It would be nice to be able to use global scheduling strategy or specify its own strategy separately when running the sample_fragment task.

Currently it is configured to use its _local_strategy or use "SPREAD".

Use case

No response
@pfldy2850 pfldy2850 added enhancement Request for new feature and/or capability triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Dec 5, 2024
@pfldy2850 pfldy2850 mentioned this issue Dec 5, 2024
Merged
8 tasks
@jcotant1 jcotant1 added the data Ray Data-related issues label Dec 5, 2024
@richardliaw richardliaw added P1 Issue that should be fixed within a few weeks and removed triage Needs triage (eg: priority, bug/not-bug, and owning component) labels Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
data Ray Data-related issues enhancement Request for new feature and/or capability P1 Issue that should be fixed within a few weeks
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@richardliaw @pfldy2850 @jcotant1