[requirements] Add PyArrow to ray[tune] dependencies #34397
Merged
Conversation
This file contains 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
added 2 commits
April 14, 2023 15:18
Signed-off-by: Kai Fricke <kai@anyscale.com>
Signed-off-by: Kai Fricke <kai@anyscale.com>
ericl
approved these changes
Apr 14, 2023
vitsai
pushed a commit
to vitsai/ray
that referenced
this pull request
Apr 17, 2023
Ray Tune depends on PyArrow for filesyncing. However, `ray[tune]` currently does not include pyarrow as a dependency, which means version constraints are not enforced and syncing is not guaranteed to work out of the box. This surfaced as a problem when a user used poetry with `ray[tune]` as a constraint, but an incompatible version of pyarrow was installed. In this case, syncing to cloud storage was broken. Signed-off-by: Kai Fricke <kai@anyscale.com>
elliottower
pushed a commit
to elliottower/ray
that referenced
this pull request
Apr 22, 2023
Ray Tune depends on PyArrow for filesyncing. However, `ray[tune]` currently does not include pyarrow as a dependency, which means version constraints are not enforced and syncing is not guaranteed to work out of the box. This surfaced as a problem when a user used poetry with `ray[tune]` as a constraint, but an incompatible version of pyarrow was installed. In this case, syncing to cloud storage was broken. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: elliottower <elliot@elliottower.com>
ProjectsByJackHe
pushed a commit
to ProjectsByJackHe/ray
that referenced
this pull request
May 4, 2023
Ray Tune depends on PyArrow for filesyncing. However, `ray[tune]` currently does not include pyarrow as a dependency, which means version constraints are not enforced and syncing is not guaranteed to work out of the box. This surfaced as a problem when a user used poetry with `ray[tune]` as a constraint, but an incompatible version of pyarrow was installed. In this case, syncing to cloud storage was broken. Signed-off-by: Kai Fricke <kai@anyscale.com> Signed-off-by: Jack He <jackhe2345@gmail.com>
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?
Ray Tune depends on PyArrow for filesyncing. However,
ray[tune]currently does not include pyarrow as a dependency, which means version constraints are not enforced and syncing is not guaranteed to work out of the box.This surfaced as a problem when a user used poetry with
ray[tune]as a constraint, but an incompatible version of pyarrow was installed. In this case, syncing to cloud storage was broken.Related issue number
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.