[
https://issues.apache.org/jira/browse/GEODE-8741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17319780#comment-17319780
]
Anilkumar Gingade commented on GEODE-8741:
------------------------------------------
[~mivanac]
I have to look into the PR to see what your are really are trying to achieve in
this ticket. It will be helpful if you can add more information with the
example (depending on the issue).
E.g.
Avoid sending CQ events for specific CQ query-operations (E.g. destroy Query
operation) to client.
For a region.put() which results in CQ event with its query operation as
destroy; avoid sending this event to client.
I am not seeing any value/scenario that needs this kind of behavior. Do you
have any example can you please explain here.
The core CQ design aspect was to establish a data view representing a query
result that can be expressed in the form of query. And support event mechanism
that will enable to manage/maintain that view as the change happens on the
source data. The changes requested in this ticket, breaks the core design and
can allow one to represent/establish a different data view that is not in-line
with the source data (a query result view). I don't see need for supporting
that kind of behavior in the server side. If Client is not interested to see
specific event/operation it should be filtering this out on the client side.
Why the need for this behavior?
Looking the Pull Request opened; its not like its avoiding processing of CQs,
which is generally more expensive part of having CQ; only thing its avoiding
sending the CQ event to client. If this is the behavior client/application is
looking for; probably CQ is not the functionality to use.
Also, it will be nice to use Request For Change (RFC) process for any issues
that has behavior/functional or new API requirements. It will help to get
feedback during design phase itself.
> Filter out CQ Create/Update/Destroy notifications
> -------------------------------------------------
>
> Key: GEODE-8741
> URL: https://issues.apache.org/jira/browse/GEODE-8741
> Project: Geode
> Issue Type: Wish
> Components: cq
> Reporter: Mario Ivanac
> Assignee: Mario Ivanac
> Priority: Minor
> Labels: pull-request-available
>
> Clients subscribe to server-side events by using SQL-type query filtering.
> The server sends all events that modify the query results. CQ event delivery
> uses the client/server subscription framework.
> We want possibility for each client to block/suppress CQ
> Create/Update/Destroy event (notification).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
