[
https://issues.apache.org/jira/browse/GEODE-8943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294943#comment-17294943
]
ASF GitHub Bot commented on GEODE-8943:
---------------------------------------
lgtm-com[bot] commented on pull request #6075:
URL: https://github.com/apache/geode/pull/6075#issuecomment-790233665
This pull request **introduces 2 alerts** when merging
21b6de7598fa690f65fe918e5a24ee37840913c5 into
c650095d74ca0b88a33a1089a0e0caa331b42ea0 - [view on
LGTM.com](https://lgtm.com/projects/g/apache/geode/rev/pr-890925863de2981aa1a6e086fb1e785d68b098c7)
**new alerts:**
* 2 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)
