akhilesh-delphix commented on issue #1078:
URL: 
https://github.com/apache/iceberg-python/issues/1078#issuecomment-7063128426

   Thanks for the work on this. I have a use case on the merge-on-read side and 
wanted to check how it fits the plans in this issue.
   
   **Use case:** I copy a table's data files to a new table location. The 
source has v2 position delete files. I rewrite the `file_path` column inside 
each position delete file so it points at the copied data file path, and upload 
the result. I then need to register those delete files in the target table's 
metadata (a `DELETES` manifest and a snapshot), so readers apply them.
   
   **What I found on `main` (commit `535425d`, Nov 21, 2026):**
   - `ManifestWriterV1` and `ManifestWriterV2` return `ManifestContent.DATA` 
only.
   - `add_files` builds `DataFile` entries with `DataFileContent.DATA` only.
   - I found no API to register existing delete files. In Java this is 
`RowDelta.addDeletes(DeleteFile)`.
   - Related work I found: #3618 (position-delete writes from 
`Transaction.delete()`), #3131 (`replace()` for data files only; delete 
manifests are passed through), and #2787 / #4459 (remove data files by path).
   
   **Questions:**
   1. Is a `RowDelta`-style API, which commits existing position and equality 
delete files in a `DELETES` manifest, part of the plan for this issue? Or 
should it be tracked separately?
   2. The June plan mentions v3 deletion vectors. Would a v2 position-delete 
path still be supported, as kevinjqliu's January comment suggests?
   3. If it isn't planned, would a contribution that adds a delete manifest 
writer and a snapshot producer taking delete file descriptors (path, format, 
size, record count, partition) be welcome? Reading, applying and committing are 
separate concerns, so it could be separate from the writing of new delete files.
   
   Happy to test a branch against my setup.
   


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