Closed
Description
Today, when restoring we assert that the descriptors that we're publishing PUBLIC have not changed since they were added in the OFFLINE state. We are seeing that there are cases where this assertion is failing. This is not ideal since we perform this check at the end of what could be a potentially lengthy restore. This assertion is enforced via a CPut.
This issue proposes that we instead always mark the table as public, but also log:
- The current value of the OFFLINE descriptor that we read just before changing the state to PUBLIC
- The expected value that we are currently
CPutting against. - The expected value that we would have read with this patch backupccl: fix bug due to transaction restart while publishing descri… #54748.