GEODE-6013: Use expected initial image requester's rvv information#2857
GEODE-6013: Use expected initial image requester's rvv information#2857agingade merged 1 commit intoapache:developfrom
Conversation
Re-submitting after fixing NPE from previous checkin. Made changes to use the expected initial image requester's rvv information instead of the image provider's local rvv while determining full or delta GII. There was logical error where it was using provider's local exception(rvv) instead of using requester's local exception(rvv). This could result in performing Delta GII instead of Full GII.
|
For other reviewers, here is a diff between Anil's last PR and this one: |
There was a problem hiding this comment.
Hi Anil, can you explain what the difference is between this PR and your last one? I see that you have a new test but the RVV changes seem exactly the same to me. You've changed one line to use dominates() instead of isNewerThanOrCanFillExceptionsFor() but the effect seems the same to me given the implementation of RVH.dominates().
public boolean dominates(RegionVersionHolder<T> other) {
return !other.isNewerThanOrCanFillExceptionsFor(this);
}
Bruce, as part of the fix, i was trying to refactor the code to make it more readable. In the new checkin there is no logical changes except reverting back to its original code.
In my previous checkin, in "isGCVersionDominatedByHolder()" i had changed:
return !holder.isNewerThanOrCanFillExceptionsFor(otherHolder);
TO
return otherHolder.dominates(holder);
Idea was to change from negate condition; which caused NPE as "otherHolder" could be null. To address NPE, I reverted back to the original code.
Re-submitting after fixing NPE from previous checkin.
Made changes to use the expected initial image requester's rvv
information instead of the image provider's local rvv while
determining full or delta GII.
There was logical error where it was using provider's local
exception(rvv) instead of using requester's local exception(rvv).
This could result in performing Delta GII instead of Full GII.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
[Yes ] Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
[Yes ] Has your PR been rebased against the latest commit within the target branch (typically
develop)?[Yes] Is your initial contribution a single, squashed commit?
[Yes] Does
gradlew buildrun cleanly?[Yes ] Have you written or updated unit tests to verify your changes?
[NA] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?