Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HubSpot Backport: HBASE-28502 Cleanup old backup manifest logic (#5871) #94

Merged
merged 1 commit into from
May 17, 2024

Conversation

ndimiduk
Copy link

In older versions of HBase's backup mechanism, a manifest was written per table being backed up. This was since refactored to one manifest per backup, but the manifest code was not updated. A concrete issue with the old code was that the manifest for full backups did not correctly list the tables included in the backup.

Reviewed-by: Ray Mattingly [email protected]

@bbeaudreault
Copy link
Member

Can you fixup the commit message to be HubSpot Backport: <commit message from upstream> as part of merging?

@ndimiduk ndimiduk requested a review from ksravista May 17, 2024 11:24
…he#5871)

In older versions of HBase's backup mechanism, a manifest
was written per table being backed up. This was since refactored
to one manifest per backup, but the manifest code was not updated.
A concrete issue with the old code was that the manifest
for full backups did not correctly list the tables included
in the backup.

Signed-off-by: Nick Dimiduk <[email protected]>
Reviewed-by: Ray Mattingly <[email protected]>
@rmdmattingly rmdmattingly changed the title Backport "HBASE-28502 Cleanup old backup manifest logic (#5871)" to hubspot-2.6 HubSpot Backport: HBASE-28502 Cleanup old backup manifest logic (#5871) May 17, 2024
@rmdmattingly rmdmattingly merged commit 38fe324 into hubspot-2.6 May 17, 2024
1 check passed
@rmdmattingly rmdmattingly deleted the 28502-hubspot-2.6 branch May 17, 2024 19:58
rmdmattingly pushed a commit that referenced this pull request May 21, 2024
…he#5871) (#94)

In older versions of HBase's backup mechanism, a manifest
was written per table being backed up. This was since refactored
to one manifest per backup, but the manifest code was not updated.
A concrete issue with the old code was that the manifest
for full backups did not correctly list the tables included
in the backup.

Reviewed-by: Ray Mattingly <[email protected]>

Signed-off-by: Nick Dimiduk <[email protected]>
Co-authored-by: DieterDP <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants