Hi Vinod, The problem of moving an Iceberg table is the absolute path within the metadata layer. They may not work once you move it from one place to another. Here are solutions: 1. Make sure the paths are the same, or it works across regions. For example, you can use https://docs.aws.amazon.com/AmazonS3/latest/userguide/MultiRegionAccessPoints.html. It is supported in Iceberg by PRs https://github.com/apache/iceberg/pull/4391, https://github.com/apache/iceberg/pull/4334. This solution relies on s3's replication and you may want to check the integrity of the table periodically. 2. Relative path, which is WIP, check https://github.com/apache/iceberg/issues/1617 for more information. 3. Replace the old paths with the new ones when you copy the table. I got a PR(https://github.com/apache/iceberg/pull/4705) for that. It works well for us. Will split it and submit for review later.
Best, Yufei On Tue, Jun 28, 2022 at 11:58 AM Vinod Kumar Mullangi <vmulla...@expediagroup.com.invalid> wrote: > Hi Team, > > > > I am working as a Data Engineer in Expedia. > > As part of one of my projects. I am doing some research on process for > backing up and restoring iceberg tables(stored in aws s3) so that we can > recover data if an Iceberg table is accidentally dropped. > > I went over few documentations but not able to get exact process. > > It will be helpful if you can send any documentations or references for > this. > > > > Regards, > > Vinod >