-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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] refine concepts in user-facing APIs #40725
Labels
data
Ray Data-related issues
data-ux
ray 2.9
Issues targeting Ray 2.9 release (~Q4 CY2023)
release-blocker
P0 Issue that blocks the release
Comments
raulchen
added
P1
Issue that should be fixed within a few weeks
data
Ray Data-related issues
ray 2.9
Issues targeting Ray 2.9 release (~Q4 CY2023)
labels
Oct 26, 2023
@c21 planning to do for this week. |
anyscalesam
added
ray 2.10
ray 2.9
Issues targeting Ray 2.9 release (~Q4 CY2023)
and removed
ray 2.9
Issues targeting Ray 2.9 release (~Q4 CY2023)
ray 2.10
labels
Dec 4, 2023
@c21 can you link the PR; only remaining is docs. sitll on track for ray29 |
8 tasks
c21
added
release-blocker
P0 Issue that blocks the release
and removed
P1
Issue that should be fixed within a few weeks
labels
Dec 15, 2023
8 tasks
#41948 is the PR to be merged to 2.9. |
8 tasks
Did the above get picked in successfully @c21 ? |
@anyscalesam - targeting to get #41963 in by EOD today. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
data
Ray Data-related issues
data-ux
ray 2.9
Issues targeting Ray 2.9 release (~Q4 CY2023)
release-blocker
P0 Issue that blocks the release
Today, some concepts in Data APIs are either inaccurate, or unnecessary to expose. Examples are:
parallelism
currently actually means number of partitions, instead of number of concurrent tasks.TaskPoolStrategy/ActorPoolStrategy
expose too many Ray Core-level details that are hard to understand for people who only want to use Ray Data.The text was updated successfully, but these errors were encountered: