[ https://issues.apache.org/jira/browse/GEODE-8811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17272434#comment-17272434 ]
ASF subversion and git services commented on GEODE-8811: -------------------------------------------------------- Commit f8987edd090558ba17f715e7e5fdb00e898e72eb in geode's branch refs/heads/develop from Kirk Lund [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f8987ed ] GEODE-8811: Fix new value in events for failing client (#5953) * Declare parameters as interfaces instead of implementations. * Improve unit testing of CacheClientNotifier. * Use MockitoRule with STRICT_STUBS. > Create events are fired as update events > ---------------------------------------- > > Key: GEODE-8811 > URL: https://issues.apache.org/jira/browse/GEODE-8811 > Project: Geode > Issue Type: Bug > Components: cq > Reporter: Nabarun Nag > Assignee: Kirk Lund > Priority: Major > Labels: GeodeOperationAPI, blocks-1.14.0, pull-request-available > > When the failing client fires the event for an object during register > interest ... it shows the expected value as the "oldValue" (vs. the newValue) > ... and newValue == null and the OperationType as UPDATE (vs. CREATE). -- This message was sent by Atlassian Jira (v8.3.4#803005)