[
https://issues.apache.org/jira/browse/GEODE-10348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alberto Gomez updated GEODE-10348:
----------------------------------
Description:
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."
was:
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 dropped and the new update is added to the end of the queue, as
shown here for key A."
> 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: needsTriage
>
> 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)
