You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/02 17:56:00 UTC
[jira] [Commented] (GEODE-10348) Correct documentation about conflation
[ https://issues.apache.org/jira/browse/GEODE-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17545590#comment-17545590 ]
ASF subversion and git services commented on GEODE-10348:
---------------------------------------------------------
Commit 03875b8eac351ee901377155fcb841bbd3c11b10 in geode's branch refs/heads/develop from Alberto Gomez
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=03875b8eac ]
GEODE-10348: Fix documentation on conflation (#7746)
The Geode documentation states on conflation:
"When an update is added to a queue that has conflation enabled,
if there is already an update message in the queue for the
entry key, then the existing message assumes the value of the
new update and the new update is dropped, as shown here for key A."
Nevertheless, that is not correct. The actual behavior is the following:
"When an update is added to a queue that has conflation enabled,
if there is already an update message in the queue for the
entry key, then the existing message is removed and the new
update is added to the end of the queue, as shown here for key A."
The text has been updated as well as the the figure with the example.
> Correct documentation about conflation
> --------------------------------------
>
> Key: GEODE-10348
> URL: https://issues.apache.org/jira/browse/GEODE-10348
> Project: Geode
> Issue Type: Bug
> Components: docs, wan
> Reporter: Alberto Gomez
> Assignee: Alberto Gomez
> Priority: Major
> Labels: pull-request-available
>
> The Geode documentation states on conflation:
> "When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message assumes the value of the new update and the new update is dropped, as shown here for key A."
> Nevertheless, that is not correct. The actual behavior is the following:
> "When an update is added to a queue that has conflation enabled, if there is already an update message in the queue for the entry key, then the existing message is removed and the new update is added to the end of the queue, as shown here for key A."
--
This message was sent by Atlassian Jira
(v8.20.7#820007)