GitHub user shroman opened a pull request:
https://github.com/apache/ignite/pull/1920
IGNITE-5121: REST API call with empty cache name to call "default."
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shroman/ignite IGNITE-5121
Denis Magda created IGNITE-5182:
---
Summary: Document Job Stealing API Usage
Key: IGNITE-5182
URL: https://issues.apache.org/jira/browse/IGNITE-5182
Project: Ignite
Issue Type: Sub-task
Continuous queries are predicate-based. Initial query is a separate
optional feature that allows you to fetch the data that existed before
listener was registered, it does not affect further update notifications in
any way. Having said that, the behavior you observe is correct.
-Val
On Mon, May 8
I have already mentioned below that i can use remotefilterfactory with more
conditions but then this is basically the replication.
Second,
When I try ContinuousQuery I am getting events for the records I am not
subscribed to. I know that i can write the conditions again in the
remotefilterfactor
Hi Fatih.
Documentation for initial query says: "an initial query that will be
executed before the continuous query gets registered in the cluster and
before you start to receive the updates". So it will only be executed once.
To further filter events you must implement it on filter logic. Your fi
When I try ContinuousQuery I am getting events for the records I am not
subscribed to.
Entity Class
public class Profile implements Serializable{
@QuerySqlField(index = true)
private String number;
@QuerySqlField(index = true)
private Double dataUsage;
}
Updat
