Skip to content

Specify handling for unrecognized logical/physical type combinations #607

Description

@divjotarora

Describe the enhancement requested

Describe the enhancement requested

We currently do not specify how readers should handle unrecognized logical types or logical/physical type combinations. In both cases, the logical type and the stats for the relevant columns should be ignored and the reader should not fail.

This issue is split off from #600, which adds a previously unsupported logical/physical type combination (TimestampType annotating an FLBA column).

Component(s)

Core

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions