badalprasadsingh opened a new issue, #2610:
URL: https://github.com/apache/iceberg-go/issues/2610

   ### Apache Iceberg version
   
   None
   
   ### Please describe the bug 🐞
   
   after the source column of an identity partition is promoted from "float" to 
"double", an eq-delete written afterwards does not apply to data files written 
before the promotion, even though both are in the same partition. The deleted 
rows stay visible and no error is returned. This happens on v2 and v3.
   
   what I want to say is:
   
   1. table `id long, v float`, partitioned by `identity(v)`
   2. append `(1, 1.5)` and `(2, 1.5)`
   3. promote `v` to `double` with `UpdateSchema().UpdateColumn`
   4. `WriteEqualityDeletes` keyed on `id`, with the row `(id 1, v 1.5)` so it 
routes to the partition, then `RowDelta.AddDeletes` and commit
   5. the scan gives `[1 2]`, expected `[2]`
   
   The delete file and the data file are both in spec 0 with partition `v=1.5`. 
The old data file's manifest returns that value as a `float32`, and the new 
delete file's manifest returns it as a `float64`. The eq-del index keys 
partitions with `comparablePartitionKey`, which keeps `float32` and `float64` 
as different key types, so the delete never meets the data file. Integer values 
are normalized first (`equalityDeleteIntegerPartitionValue`), so `int` to 
`long` works.
   
   This is the silent counterpart of the pos-delete scan failure after the same 
promotion. Reading old manifests with the current partition type, as 
iceberg-ava does, would fix both.
   
   **Status** : will be picking this up
   


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to