Skip to content

Conversation

@dentiny
Copy link
Contributor

@dentiny dentiny commented Jul 10, 2025

What changes are included in this PR?

Motivation:

  • I would like to leverage naming mapping, to compensate the issue that table metadata reassigns field id on creation.
  • Name mapping requires (1) field id; (2) field name; (3) children values; all these information could be fetched from Schema, but could be a lot easier and performant if we could expose (1) field id -> field name; (2) field id -> field mapping.

Are these changes tested?

N/A, trivial visibility change, no functional change

Copy link
Member

@Xuanwo Xuanwo left a comment

Choose a reason for hiding this comment

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

Thank you @dentiny for this, looks not harmful.

@Xuanwo Xuanwo merged commit 55e181e into apache:main Jul 14, 2025
17 checks passed
jdcasale pushed a commit to jdcasale/iceberg-rust that referenced this pull request Jul 28, 2025
## What changes are included in this PR?

Motivation:
- I would like to leverage naming mapping, to compensate the issue that
table metadata reassigns field id on creation.
- Name mapping requires (1) field id; (2) field name; (3) children
values; all these information could be fetched from `Schema`, but could
be a lot easier and performant if we could expose (1) field id -> field
name; (2) field id -> field mapping.

## Are these changes tested?

N/A, trivial visibility change, no functional change
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