[
https://issues.apache.org/jira/browse/IGNITE-14402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17309496#comment-17309496
]
Aleksey Plekhanov commented on IGNITE-14402:
--------------------------------------------
I agree, at least we can switch from the fourth to third option at any time,
but can't switch from third to fourth due to backward compatibility.
But it's not the only problem. With JCache API (registerCacheEntryListener) we
can't configure some of continuous query parameters (page size, time interval),
also there are some JCache API parameters which can't be implemented for thin
client and should be ignored (isSynchronous, isOldValueRequired). Perhaps we
should think about an additional API to register listeners with additional
parameters or we can even reuse {{query}} method and implement ContinuousQuery
in a similar to thick client way (handle initial query internally on the
client-side). Also, we need to introduce some public API DisconnectListener to
notify about client channel failure.
I think I can return to this task next week, refactor my draft implementation
and try to implement API with thick-client like CQ. I will describe API changes
and after that, we can continue our discussion about the proposed API on dev
list. WDYT?
> Java Thin: Continuous Query
> ---------------------------
>
> Key: IGNITE-14402
> URL: https://issues.apache.org/jira/browse/IGNITE-14402
> Project: Ignite
> Issue Type: New Feature
> Components: thin client
> Reporter: Pavel Tupitsyn
> Assignee: Pavel Tupitsyn
> Priority: Major
> Labels: iep-50
> Fix For: 2.11
>
>
> Implement Continuous Query API in Java Thin Client.
> See .NET Thin Client as a reference: IGNITE-13148
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
