github-actions[bot] commented on issue #8979:
URL: https://github.com/apache/iceberg/issues/8979#issuecomment-2412570619
This issue has been closed because it has not received any activity in the
last 14 days since being marked as 'stale'
--
This is an automated message from the Apache Gi
github-actions[bot] closed issue #8979: Data duplicate after the partition is
modified
URL: https://github.com/apache/iceberg/issues/8979
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific
github-actions[bot] commented on issue #8979:
URL: https://github.com/apache/iceberg/issues/8979#issuecomment-2381033361
This issue has been automatically marked as stale because it has been open
for 180 days with no activity. It will be closed in next 14 days if no further
activity occurs.
nastra commented on issue #8979:
URL: https://github.com/apache/iceberg/issues/8979#issuecomment-1792399213
@jiamin13579 you might want to take a look at
https://iceberg.apache.org/docs/latest/evolution/#partition-evolution.
> Partition evolution is a metadata operation and does not e
jiamin13579 opened a new issue, #8979:
URL: https://github.com/apache/iceberg/issues/8979
### Query engine
Spark
### Question
When we talk about writing data to Iceberg, it is common practice to first
issue an eqDelete record and then write a data record. However, after
