c-thiel opened a new issue, #12809:
URL: https://github.com/apache/iceberg/issues/12809
### Apache Iceberg version
1.8.1 (latest release)
### Query engine
Spark
### Please describe the bug 🐞
Lets assume the following changes:
1. ViewVersion 1 is added and set active
2. View Version 2 is added and set active
3. View Version 1 is set active.
This resulted in the following `version_log`:
```json
"version-log": [
{
"version-id": 1,
"timestamp-ms": 1744716416168
},
{
"version-id": 2,
"timestamp-ms": 1744716449754
},
{
"version-id": 1,
"timestamp-ms": 1744716416168
}
],
```
Note that the last and first entries have the same timestamp, namely the
timestamp of the initial ViewVersion creation.
I believe this is undesired in a history, where we are interested when a
certain change became active. It makes sense to use the exact timestamp of the
ViewVersion if it was added in the same set of changes, but re-enabling a
previously used view version (maybe years ago) should not add a history for
this past timestamp.
Fix in Rust: https://github.com/apache/iceberg-rust/pull/1218
The problematic line in Java is here:
https://github.com/apache/iceberg/blob/cc4fe4cc50043ccba89700f7948090ff87a5baee/core/src/main/java/org/apache/iceberg/view/ViewMetadata.java#L254
### Willingness to contribute
- [ ] I can contribute a fix for this bug independently
- [ ] I would be willing to contribute a fix for this bug with guidance from
the Iceberg community
- [ ] I cannot contribute a fix for this bug at this time
--
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: issues-unsubscr...@iceberg.apache.org.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@iceberg.apache.org
For additional commands, e-mail: issues-h...@iceberg.apache.org
