You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Right now we don't show the initial-default and write-default in the repr of the NestedField. This is because we use it internally to deserialize the Iceberg metadata. With V3, this will also be exposed to the user. It would be good to include these in the repr if they are set. This will not change the repr for existing NestedFields, but it will show it for the ones that have an initial default. The first step would be to look into Pydantic if we can make this conditional.
The text was updated successfully, but these errors were encountered:
@kevinjqliu I looked into the mentioned PR. I can see Fokko has already finished changes for initial-default. 👍 I see some additional changes for write-default, are we planning to work separately on write-default or it'll be part of same PR ?
If Fokko is already working on write-default, I will follow along the changes as I am still getting familiar with codebase and following such changes will help me understand it better.
Feature Request / Improvement
Right now we don't show the
initial-default
andwrite-default
in therepr
of theNestedField
. This is because we use it internally to deserialize the Iceberg metadata. With V3, this will also be exposed to the user. It would be good to include these in the repr if they are set. This will not change the repr for existingNestedField
s, but it will show it for the ones that have an initial default. The first step would be to look into Pydantic if we can make this conditional.The text was updated successfully, but these errors were encountered: