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

Cannot read Parquet files with missing dictionary page offsets #5764

Closed
abaranec opened this issue Jul 12, 2024 · 0 comments · Fixed by #5765
Closed

Cannot read Parquet files with missing dictionary page offsets #5764

abaranec opened this issue Jul 12, 2024 · 0 comments · Fixed by #5765
Assignees
Labels
bug Something isn't working core Core development tasks parquet Related to the Parquet integration
Milestone

Comments

@abaranec
Copy link
Contributor

abaranec commented Jul 12, 2024

Description
An older parquet file that is missing the dictionary_page_offset.

Steps to reproduce
Attempt to load the attached file

Expected results
You get a table and no errors

Actual results

Errors

Additional details and attachments

data.tar.gz

Versions

  • Deephaven: 0.33.4
@abaranec abaranec added bug Something isn't working triage labels Jul 12, 2024
@abaranec abaranec added this to the 0.36.0 milestone Jul 12, 2024
@abaranec abaranec self-assigned this Jul 12, 2024
@abaranec abaranec changed the title Cannot read Parquet files with missing dictionary page offsets or null INT96 values Cannot read Parquet files with missing dictionary page offsets Jul 12, 2024
@rcaudy rcaudy added core Core development tasks parquet Related to the Parquet integration and removed triage labels Jul 12, 2024
abaranec added a commit to abaranec/deephaven-core that referenced this issue Jul 18, 2024
devinrsmith pushed a commit that referenced this issue Jul 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working core Core development tasks parquet Related to the Parquet integration
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants