Skip to content

GH-607: Specify handling for unrecognized logical types #606

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.

Sign up for GitHub

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

Open
divjotarora wants to merge 1 commit into
base: master
Choose a base branch
from
Open

GH-607: Specify handling for unrecognized logical types #606

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions LogicalTypes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,6 +40,8 @@ according to well defined conversion rules.

### Compatibility

#### ConvertedType

The Thrift definition of the metadata has two fields for logical types: `ConvertedType` and `LogicalType`.
`ConvertedType` is an enum of all available annotations. Since Thrift enums can't have additional type parameters,
it is cumbersome to define additional type parameters, like decimal scale and precision
Expand All @@ -54,6 +56,13 @@ in case `LogicalType` annotations are not present. Parquet writers must always w
`LogicalType` annotations where applicable, but must also write the corresponding
`ConvertedType` annotations (if any) to maintain compatibility with old readers.

#### Unsupported Logical Types

When reading a file written by a newer writer that contains an unrecognized logical type or an
unrecognized logical/physical type combination on a column, readers should ignore both the logical
type annotation and statistics for that column. Only the physical type information should be used
to process the column's data.

Compatibility considerations are mentioned for each annotation in the corresponding section.

## String Types
Expand Down