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

GEODE-6260: Do not cleanup non-dirty entries in transactional set operation #3060

Merged
merged 2 commits into from Jan 9, 2019

Conversation

pivotal-eshu
Copy link
Contributor

No description provided.

@@ -1540,6 +1540,11 @@ protected TXEntryState txReadEntry(KeyInfo keyInfo, InternalRegion internalRegio
txr = txWriteRegion(internalRegion, keyInfo);
}
result = dataReg.createReadEntry(txr, keyInfo, createIfAbsent);
if (result == null) {
assert !createIfAbsent;
Copy link
Contributor

Choose a reason for hiding this comment

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

Does "!createIfAbsent" indicate that this is a set operation? If so I think you should add a comment here.
Something like "createReadEntry will only returns null if createIfAbsent is false. CreateIfAbsent will only be false when this method is called by set operations. In that case we do not want the TXState to have a TXEntryState."

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will make the changes by using the more descriptive comments.

@pivotal-eshu pivotal-eshu merged commit 8a9d999 into develop Jan 9, 2019
@pivotal-eshu pivotal-eshu deleted the feature/GEODE-6260 branch January 11, 2019 21:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants