NotaSimpO opened a new issue, #11645:
URL: https://github.com/apache/iceberg/issues/11645

   I'm working with Apache Iceberg on my local setup, using tools like Apache 
Spark, Nessie, and MinIO. I need to move Parquet data files from one location 
(standardize/location1) to another (standardize/location2). I've updated the 
manifest file to reflect the new data paths, and the table is partially working 
in the new location.
   
   However, I'm facing a problem with Iceberg recognizing delete files. 
Specifically, the delete files (which track deleted file paths and the 
positions of deleted data) also contain the original file paths. Even after 
updating these paths to the new location, Iceberg still doesn't recognize the 
delete files correctly, and the table's behavior remains inconsistent.
   
   How can I handle this issue effectively? Is there a way to move the table 
and its associated files (including delete files) properly so Iceberg 
recognizes them? I would prefer a solution in PySpark or SQL..
   
   Thank


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

Reply via email to