McKMarcBruchner commented on issue #14606: URL: https://github.com/apache/iceberg/issues/14606#issuecomment-3546052490
@manuzhang my problem is the following in terms of disaster recovery: * I have an original-bucket where our running data lives on * I have a backup-bucket where we take backups of the original buckets * Then if disaster strikes, the original-bucket is corrupted, lost, or in any other way unaccessible for me * That means I only have access to my backup-bucket, that has a snapshot of the data of the original-bucket * Meaning I have the data and metadata on the backup-bucket, but the metadata files still contain the `s3a://oringal-bucket` path * It is not guaranteed that we can ever go back or reuse the original-bucket name, because bucket names in s3 are global * Therefore, I would need to be able to run `rewrite_table_path` on the backup-bucket with the metadata files still containing `s3a://oringal-bucket` without registering it first. [This blog](dremio.com/blog/disaster-recovery-for-apache-iceberg-tables-restoring-from-backup-and-getting-back-online/#h-best-practices-for-backing-up-and-restoring-iceberg-tables) states that this should be possible, but I don't see it. -- 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]
