Skip to content

Conversation

@swamirishi
Copy link
Contributor

@swamirishi swamirishi commented Dec 24, 2025

What changes were proposed in this pull request?

Revert the patch HDDS-13415 and do individual deletes on snapshot create

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-14240

How was this patch tested?

Existing tests should be sufficient since we are reverting a patch

…ntation

This reverts commit ae92a18

Change-Id: I2ed4e78d395fb48ba0769c2f8319fb6686f03a70
@swamirishi swamirishi requested a review from szetszwo December 24, 2025 19:26
Copy link
Contributor

@szetszwo szetszwo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

+1 the change looks good.

@adoroszlai
Copy link
Contributor

since we are reverting a patch

Please do not create Jira issue for reverting another. Just use the original ticket, like:

* 00c935b729 Revert "HDDS-13776. Fail DirectoryPurge requests if previous snapshot ID validation fails. (#9130)"
* aee5aa31a7 Revert "HDDS-13814. Bump opentelemetry to 1.55.0 (#9170)"
* 3e5414d010 Revert "HDDS-13213. KeyDeletingService should limit task size by both key count and serialized size. (#8757)" (#8957)

@swamirishi swamirishi marked this pull request as ready for review December 25, 2025 00:06
@swamirishi
Copy link
Contributor Author

Please do not create Jira issue for reverting another. Just use the original ticket, like:

I believe havong another jira for revert makes sense. This is not exactly a full exact revert so it makes sense to have a separate jira.

@swamirishi swamirishi merged commit 90f62ad into apache:master Dec 25, 2025
94 of 96 checks passed
@swamirishi
Copy link
Contributor Author

Thank you @szetszwo for reviewing the patch

@adoroszlai
Copy link
Contributor

This is not exactly a full exact revert

It fully reverts HDDS-13415, and an additioonal usage of deleteRangeWithBatch introduced later.

@szetszwo
Copy link
Contributor

@swamirishi , when someone has a concern, it is better to finish the discussion first. Please don't merge the PR so early. Thanks.

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.

3 participants