[
https://issues.apache.org/jira/browse/GEODE-8247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mario Ivanac updated GEODE-8247:
--------------------------------
Description:
When updating entries in Partition region, inside transaction,
CQ sends UPDATE events instead of CREATE.
Deeper analysis shows, that in failure case,
FilterProfile.getFilterRoutingInfoPart1 and
FilterProfile.getFilterRoutingInfoPart2 are called consecutively for the same
event (CREATE).
So when getFilterRoutingInfoPart2 calls second time CqService to process the
same EntryEvent,
it interprets it as UPDATE.
{color:#ffc66d} {color}
was:
When updating entries in Partition region, inside transaction,
CQ sends UPDATE events instead of CREATE.
Deeper analysis shows, that in this case
FilterProfile.getFilterRoutingInfoPart1 and
FilterProfile.getFilterRoutingInfoPart2 are called consecutively for the same
event.
So when getFilterRoutingInfoPart2 calls second time CqService to process
EntryEvent,
it interprets it as UPDATE.
{color:#ffc66d} {color}
> CQs sends back wrong event (UPDATE instead of CREATE)
> --------------------------------------------------------
>
> Key: GEODE-8247
> URL: https://issues.apache.org/jira/browse/GEODE-8247
> Project: Geode
> Issue Type: Bug
> Components: cq
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Major
>
> When updating entries in Partition region, inside transaction,
> CQ sends UPDATE events instead of CREATE.
> Deeper analysis shows, that in failure case,
> FilterProfile.getFilterRoutingInfoPart1 and
> FilterProfile.getFilterRoutingInfoPart2 are called consecutively for the same
> event (CREATE).
> So when getFilterRoutingInfoPart2 calls second time CqService to process the
> same EntryEvent,
> it interprets it as UPDATE.
> {color:#ffc66d} {color}
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
