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

Docs: clarify when the parquet reader will read from object store when using cached metadata #10909

Merged
merged 1 commit into from
Jun 14, 2024

Conversation

alamb
Copy link
Contributor

@alamb alamb commented Jun 14, 2024

Which issue does this PR close?

Part of #10580

Rationale for this change

While working on #10701 it was quite unclear to me why the parquet reader was doing a second object store request even when I had passed it pre-existing ParquetMetadata

It turns out the it was because the cached ParquetMetadata didn't have the page index strutures loaded, and so the parquet exec will load them on demand if required.

What changes are included in this PR?

Are these changes tested?

  1. Add documentation

Note: I documented this in arrow-rs too: apache/arrow-rs#5887

Are there any user-facing changes?

@alamb alamb changed the title Docs: clarify when the reader will read from object store when using cached metadata Docs: clarify when the parquet reader will read from object store when using cached metadata Jun 14, 2024
Copy link
Contributor

@comphead comphead left a comment

Choose a reason for hiding this comment

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

lgtm thanks @alamb

@comphead comphead merged commit 8f76ac5 into apache:main Jun 14, 2024
23 of 25 checks passed
findepi pushed a commit to findepi/datafusion that referenced this pull request Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants