Skip to content

Question on field id reassignment on table metadata creation #1499

Open
@dentiny

Description

@dentiny

Is your feature request related to a problem or challenge?

Hi community, I'm confused why do we need to reassign field id on table (metadata) creation?

Imagine such a case, iceberg table is periodically flushed / persisted, after data file in parquet have been persisted locally or remotely.

When table metadata is created, all field ids within schema get reassigned, which means we have mismatch for parquet file and iceberg metadata -> query engine would fail.

I'm wondering if that's necessary? Or we could provide an option to avoid?

Describe the solution you'd like

No response

Willingness to contribute

None

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions