ray
ray copied to clipboard
[RLlib; Offline RL] Add cloud filesystems to offline data input arguments.
Why are these changes needed?
So far, output/write arguments offered the users already to define cloud filesystems (like GCS, S3, ABS) to write to. This PR proposes the same arguments for input/read processes. Theoretically, this could have been passed in by the user to the input_read_method_kwargs
by setting up the filesystem object before building the AlgorithmConfig
, but would be less comfortable and probably more error-prone.
This PR allows (similar to the output arguments) only GCS, S3, and ABS filesystems to be used.
Related issue number
Checks
- [x] I've signed off every commit(by using the -s flag, i.e.,
git commit -s
) in this PR. - [x] I've run
scripts/format.sh
to lint the changes in this PR. - [x] I've included any doc changes needed for https://docs.ray.io/en/master/.
- [ ] I've added any new APIs to the API Reference. For example, if I added a
method in Tune, I've added it in
doc/source/tune/api/
under the corresponding.rst
file.
- [ ] I've added any new APIs to the API Reference. For example, if I added a
method in Tune, I've added it in
- [ ] I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
- Testing Strategy
- [ ] Unit tests
- [ ] Release tests
- [ ] This PR is not tested :(