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

Correct PassThroughMergePolicy documentation [DOC-174] #1315

Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/modules/wan/pages/configuring-for-map-and-cache.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ the target map if it does not exist in the target map.
* `HigherHitsMergePolicy`: Incoming entry merges from the source map to
the target map if the source entry has more hits than the target one.
* `PassThroughMergePolicy`: Incoming entry merges from the source map to
the target map unless the incoming entry is not null.
the target map unless the incoming entry is null.
* `ExpirationTimeMergePolicy`: Incoming entry merges from the source map to
the target map if the source entry will expire later than the destination entry.
Please note that this merge policy can only be used when the clusters' clocks are in sync.
Expand Down Expand Up @@ -169,7 +169,7 @@ the target cache if it does not exist in the target cache.
* `HigherHitsMergePolicy`: Incoming entry merges from the source cache to
the target cache if the source entry has more hits than the target one.
* `PassThroughMergePolicy`: Incoming entry merges from the source cache to
the target cache unless the incoming entry is not null.
the target cache unless the incoming entry is null.
* `ExpirationTimeMergePolicy`: Incoming entry merges from the source cache to
the target cache if the source entry will expire later than the destination entry.
Please note that this merge policy can only be used when the clusters' clocks are in sync.
Expand Down