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

[BACKPORT] EntryProcessor with Predicate should not touch non-matching entries #15853

Conversation

@vbekiaris
Copy link
Contributor

vbekiaris commented Oct 23, 2019

When an EntryProcessor is executed on entries filtered by a Predicate,
then non-matching entries are not accessed by the EntryProcessor.
Therefore their last access time should not be updated.

Fixes #15515 in maintenance-3.x branch

When an EntryProcessor is executed on entries filtered by a Predicate,
then non-matching entries are not accessed by the EntryProcessor.
Therefore their last access time should not be updated.
@vbekiaris vbekiaris added this to the 3.12.5 milestone Oct 23, 2019
@vbekiaris vbekiaris self-assigned this Oct 23, 2019
@vojtechtoman vojtechtoman self-requested a review Oct 24, 2019
Copy link
Contributor

vojtechtoman left a comment

Looking good to me

@vbekiaris vbekiaris requested a review from ahmetmircik Oct 29, 2019
@vbekiaris vbekiaris merged commit 6501738 into hazelcast:maintenance-3.x Oct 29, 2019
1 check passed
1 check passed
default Test PASSed.
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.