[jira] [Commented] (GEODE-1495) CQEvent is not properly getting generated after a destoy operation on Partioned Region.
[ https://issues.apache.org/jira/browse/GEODE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321803#comment-15321803 ] ASF subversion and git services commented on GEODE-1495: Commit e4994c7b3fd42b6804b909796b8589729e9861ea in incubator-geode's branch refs/heads/feature/GEODE-837 from [~agingade] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e4994c7 ] GEODE-1495: Changes are made to remove the cached destroyed token/events from the CQ. The CQEvents as seen by CQs are cached in order to avoid applying CQ queries on old values. In case of a destory CQEvent, the CQEvents are marked with destroy tokens and removed from the cache after the CQEvent is added to HAQueue. This works fine for the CQs registered locally, but for the CQs registered on peer server, the CQs weren't removed from the cache, which resulted in generating wrong CQEvent for subsequent operation. This change removes the destroy CQevent from the cache after the CQEvent is distributed to peer server. > CQEvent is not properly getting generated after a destoy operation on > Partioned Region. > --- > > Key: GEODE-1495 > URL: https://issues.apache.org/jira/browse/GEODE-1495 > Project: Geode > Issue Type: Bug > Components: cq >Reporter: Anilkumar Gingade >Assignee: Anilkumar Gingade > > In multiple server groups setup, when a CQ is registered on one server group > and that gets processed/evaluated on other server group (on which data > buckets are present), the CQ event is wrongly getting generated after a > destroy operation. > Configuration. > -- A Geode cluster with two server groups: > Server Group1 > Server Group2 > -- PR region created on both server groups, with accessor buckets/regions on > Group1 and Data bucket/regions on Group2. > -- CQ is registered on Server Group1 > For the following cache operation on Server Group2, the CQEvents are getting > generated as: > Cache op on same Key - CQEvent > > Create - Create CQEvent (as expected) > Update - The CQ is no more satisfied, Destroy CQEvent is generated (as > expected) > Update - The CQ is satisfied, but generating, Update CQEvent, instead of > Create. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-1495) CQEvent is not properly getting generated after a destoy operation on Partioned Region.
[ https://issues.apache.org/jira/browse/GEODE-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15321381#comment-15321381 ] ASF subversion and git services commented on GEODE-1495: Commit e4994c7b3fd42b6804b909796b8589729e9861ea in incubator-geode's branch refs/heads/develop from [~agingade] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=e4994c7 ] GEODE-1495: Changes are made to remove the cached destroyed token/events from the CQ. The CQEvents as seen by CQs are cached in order to avoid applying CQ queries on old values. In case of a destory CQEvent, the CQEvents are marked with destroy tokens and removed from the cache after the CQEvent is added to HAQueue. This works fine for the CQs registered locally, but for the CQs registered on peer server, the CQs weren't removed from the cache, which resulted in generating wrong CQEvent for subsequent operation. This change removes the destroy CQevent from the cache after the CQEvent is distributed to peer server. > CQEvent is not properly getting generated after a destoy operation on > Partioned Region. > --- > > Key: GEODE-1495 > URL: https://issues.apache.org/jira/browse/GEODE-1495 > Project: Geode > Issue Type: Bug > Components: cq >Reporter: Anilkumar Gingade >Assignee: Anilkumar Gingade > > In multiple server groups setup, when a CQ is registered on one server group > and that gets processed/evaluated on other server group (on which data > buckets are present), the CQ event is wrongly getting generated after a > destroy operation. > Configuration. > -- A Geode cluster with two server groups: > Server Group1 > Server Group2 > -- PR region created on both server groups, with accessor buckets/regions on > Group1 and Data bucket/regions on Group2. > -- CQ is registered on Server Group1 > For the following cache operation on Server Group2, the CQEvents are getting > generated as: > Cache op on same Key - CQEvent > > Create - Create CQEvent (as expected) > Update - The CQ is no more satisfied, Destroy CQEvent is generated (as > expected) > Update - The CQ is satisfied, but generating, Update CQEvent, instead of > Create. > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
