[ https://issues.apache.org/jira/browse/GEODE-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17296331#comment-17296331 ]
ASF GitHub Bot commented on GEODE-8943: --------------------------------------- lgtm-com[bot] commented on pull request #6075: URL: https://github.com/apache/geode/pull/6075#issuecomment-791676397 This pull request **introduces 1 alert** when merging c2993e1dc266ec8eef00e75ab92999fa72f38308 into 46f90a58c234fe0bc2719c9d9c9f8091ad460917 - [view on LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-c932ffc532f28a24669f89a92ecc3071f12f9b7a) **new alerts:** * 1 for Dereferenced variable may be null ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Filterrs (Interest and CQ) is processed multiple times with transactional > operation on PR > ----------------------------------------------------------------------------------------- > > Key: GEODE-8943 > URL: https://issues.apache.org/jira/browse/GEODE-8943 > Project: Geode > Issue Type: Bug > Components: cq, regions > Affects Versions: 1.14.0 > Reporter: Anilkumar Gingade > Assignee: Eric Shu > Priority: Major > Labels: blocks-1.14.0, pull-request-available > > The Filters (interest and CQ) could be getting processed multiple times when > transactional operation is performed. > By design on PR the filters are processed on primary bucket where the data is > applied/changed and adjunct message with interested clients are sent to > remote servers (where the subscription queues are hosted) and replicas; thus > performing filter processing once and sending the message to remote servers > only if the filters are satisfied; it looks like currently the filter > processing is happening both at the primary and secondary buckets for TX > operation. -- This message was sent by Atlassian Jira (v8.3.4#803005)