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
When we accumulate changes when doing updates to the metadata, we want to accumulate the changes in the metadata.
For example, if you first add a new column to a table, and then directly write some data, it should take the updated schema. The game goes for when you update the table properties and do a write after that, it should take the table properties into account.
This is an important concept that's currently not working of PyIceberg. For example, an upsert operation in PyIceberg is modeled as first a delete, and then an append operation. This way we want to stack the operations.
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
Feature Request / Improvement
When we accumulate changes when doing updates to the metadata, we want to accumulate the changes in the metadata.
For example, if you first add a new column to a table, and then directly write some data, it should take the updated schema. The game goes for when you update the table properties and do a write after that, it should take the table properties into account.
This is an important concept that's currently not working of PyIceberg. For example, an upsert operation in PyIceberg is modeled as first a delete, and then an append operation. This way we want to stack the operations.
The text was updated successfully, but these errors were encountered: