DieterDP-ng commented on PR #6294: URL: https://github.com/apache/hbase/pull/6294#issuecomment-2401609226
> @DieterDP-ng I've thought about it a little bit more, and I'm less sure about taking the path out of the BackupManifest. I like that the backups can be used, even if the original cluster and/or its backup system table has been lost. > > If we removed this metadata from the backup itself, and the system table were lost, then we'd put more burden on the operator to provide additional details/args I'm not seeing the detriment. What exactly would become harder if the path is no longer stored inside the manifest? - In case the operator wants to restore a backup, while the system table is still present, they'll have to do a `hbase restore s3://...`. (If they forget the path, they can retrieve it using `hbase backup history`.) - In case the operator want to restore a backup on an empty cluster, they'll have to do a `hbase restore s3://...`. -- 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]
