LuciferYang opened a new issue, #10246: URL: https://github.com/apache/paimon/issues/10246
### Search before asking - [X] I searched in the [issues](https://github.com/apache/paimon/issues) and found nothing similar. ### Paimon version master ### Compute Engine Flink / Spark (Iceberg compatibility) ### Minimal reproduce step Paimon lets several tags point at the same snapshot. When Iceberg compatibility is enabled (`metadata.iceberg.storage`), each commit rebuilds the Iceberg `refs` map from `TagManager.tags()`, but `IcebergCommitCallback` keeps only the first tag name of each snapshot (`entry.getValue().get(0)`). The other sibling tags of that snapshot disappear from the Iceberg metadata on the next commit. Repro: enable Iceberg storage, create two tags on the same snapshot, then run one more write/commit. ### What doesn't meet your expectations? Every tag of a snapshot should be exported as its own Iceberg ref. Instead, only one survives, so VERSION AS OF for a dropped sibling tag fails even though the Paimon tag still exists, and which sibling survives is nondeterministic because the tag order comes from filesystem listing in `TagManager.tagPaths`. ### Anything else? _No response_ ### Are you willing to submit a PR? - [X] I'm willing to submit a PR! -- 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 comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
