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.

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] Persist unresolved paths in FileBasedDataSource. #51424

Conversation

JDarDagran
Copy link
Contributor

Why are these changes needed?

This PR adds support for storing the original, unresolved paths in the FileBasedDatasource class. This allows components to access the raw path pattern provided by the user before any path resolution or expansion occurs.

This also adds consistency with ParquetDatasource and _FileDatasink.

Related issue number

Checks

  • I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
  • I've run scripts/format.sh to lint the changes in this PR.
  • 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 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 :(

Signed-off-by: Jakub Dardzinski <kuba0221@gmail.com>
@JDarDagran JDarDagran requested a review from a team as a code owner March 17, 2025 15:12
@JDarDagran JDarDagran changed the title Persist unresolved paths in FileBasedDataSource. [Data] Persist unresolved paths in FileBasedDataSource. Mar 17, 2025
@richardliaw richardliaw added go add ONLY when ready to merge, run all tests data Ray Data-related issues labels Mar 17, 2025
@richardliaw richardliaw merged commit 6412808 into ray-project:master Mar 17, 2025
5 checks passed
park12sj pushed a commit to park12sj/ray that referenced this pull request Mar 18, 2025
…51424)

<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

This PR adds support for storing the original, unresolved paths in the
`FileBasedDatasource` class. This allows components to access the raw
path pattern provided by the user before any path resolution or
expansion occurs.

This also adds consistency with
[`ParquetDatasource`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/_internal/datasource/parquet_datasource.py#L202)
and
[`_FileDatasink`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/datasource/file_datasink.py#L66).

## Related issue number

<!-- For example: "Closes ray-project#1234" -->

## 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.
- [ ] 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.
- [x] 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
   - [x] This PR is not tested :(

Signed-off-by: Jakub Dardzinski <kuba0221@gmail.com>
Drice1999 pushed a commit to Drice1999/ray that referenced this pull request Mar 23, 2025
…51424)

<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

This PR adds support for storing the original, unresolved paths in the
`FileBasedDatasource` class. This allows components to access the raw
path pattern provided by the user before any path resolution or
expansion occurs.

This also adds consistency with
[`ParquetDatasource`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/_internal/datasource/parquet_datasource.py#L202)
and
[`_FileDatasink`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/datasource/file_datasink.py#L66).

## Related issue number

<!-- For example: "Closes ray-project#1234" -->

## 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.
- [ ] 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.
- [x] 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
   - [x] This PR is not tested :(

Signed-off-by: Jakub Dardzinski <kuba0221@gmail.com>
dhakshin32 pushed a commit to dhakshin32/ray that referenced this pull request Mar 27, 2025
…51424)

<!-- Thank you for your contribution! Please review
https://github.com/ray-project/ray/blob/master/CONTRIBUTING.rst before
opening a pull request. -->

<!-- Please add a reviewer to the assignee section when you create a PR.
If you don't have the access to it, we will shortly find a reviewer and
assign them to your PR. -->

## Why are these changes needed?

This PR adds support for storing the original, unresolved paths in the
`FileBasedDatasource` class. This allows components to access the raw
path pattern provided by the user before any path resolution or
expansion occurs.

This also adds consistency with
[`ParquetDatasource`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/_internal/datasource/parquet_datasource.py#L202)
and
[`_FileDatasink`](https://github.com/ray-project/ray/blob/936539ce15bffa8dfa0a519fee2c7c8c0ee341b8/python/ray/data/datasource/file_datasink.py#L66).

## Related issue number

<!-- For example: "Closes ray-project#1234" -->

## 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.
- [ ] 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.
- [x] 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
   - [x] This PR is not tested :(

Signed-off-by: Jakub Dardzinski <kuba0221@gmail.com>
Signed-off-by: Dhakshin Suriakannu <d_suriakannu@apple.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
data Ray Data-related issues go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants