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] Add override_num_blocks parameter to get_parquet_metadata_provider #45767

Merged
merged 1 commit into from
Jun 5, 2024

Conversation

bveeramani
Copy link
Member

Why are these changes needed?

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: Balaji Veeramani <[email protected]>
@bveeramani bveeramani enabled auto-merge (squash) June 5, 2024 20:37
@github-actions github-actions bot added the go add ONLY when ready to merge, run all tests label Jun 5, 2024
@@ -13,7 +13,7 @@ def get_generic_metadata_provider(file_extensions: Optional[List[str]]):
return DefaultFileMetadataProvider()


def get_parquet_metadata_provider():
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, would it be better to add all read_parquet parameters?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or pass in the ParquetDatasource as the parameter?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, would it be better to add all read_parquet parameters?

What would the motivation for this? To make the signature less arbitrary?

or pass in the ParquetDatasource as the parameter?

ParquetDatasource doesn't have the value of override_num_blocks, so I'm not sure if that'd work.

Copy link
Contributor

@raulchen raulchen Jun 5, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What would the motivation for this? To make the signature less arbitrary?

just in case we'll need more info for determining metadata provider in the future.
Not a big deal though, if it requires too much work, we can revisit this later.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Gotcha. Given that we might not even use the _default_metadata_provider approach going forward, let's revisit later

@bveeramani bveeramani disabled auto-merge June 5, 2024 20:50
@bveeramani bveeramani merged commit e233555 into ray-project:master Jun 5, 2024
7 checks passed
@bveeramani bveeramani deleted the override-num-blocks branch June 5, 2024 22:19
ryanaoleary pushed a commit to ryanaoleary/ray that referenced this pull request Jun 6, 2024
yucai pushed a commit to yucai/ray that referenced this pull request Jun 6, 2024
ryanaoleary pushed a commit to ryanaoleary/ray that referenced this pull request Jun 6, 2024
yucai pushed a commit to yucai/ray that referenced this pull request Jun 7, 2024
richardsliu pushed a commit to richardsliu/ray that referenced this pull request Jun 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
go add ONLY when ready to merge, run all tests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants