...
ID | IEP-50 | ||||||||
Author | |||||||||
Sponsor | |||||||||
Created |
| ||||||||
Status |
|
Table of Contents |
---|
...
Remote Filter is a BinaryObject
:
...
ContinuousQueryWithTransformer
is out of scope: it is a separate class, and should have a separate client operation.
Initial Query functionality is excluded intentionally, it does not bring value due to lack of guarantees - see dev list threads linked below.
Name | Code |
---|---|
OP_QUERY_CONTINUOUS | 2006 |
OP_QUERY_CONTINUOUS_EVENT_NOTIFICATION | 2007 |
OP_QUERY_CONTINUOUS starts the query.
Existing OP_RESOURCE_CLOSE should be used to stop stops the continuous query using the id provided in the OP_QUERY_CONTINUOUS response message.
...
Request | |
---|---|
int | cacheId |
byte | flags: standard cache flags, see ClientCacheRequest. Only KEEP_BINARY is applicable to Continuous Query. When KEEP_BINARY is set, the filter should receive key/val in binary form. |
int | bufferSize (see AbstractContinuousQuery, default 1) |
long | timeInterval (see AbstractContinuousQuery, default 0) |
bool | includeExpired (see AbstractContinuousQuery, default false) |
BinaryObject | filter |
byte | filterPlatform (see ClientCacheScanQueryRequest, 1= Java, 2 = .NET) (when filter is not null) |
byte | initialQueryType (0 = NONE, 1 = SQL, 2 = SCAN) |
initialQuery (when initialQueryType > 0) | when initialQueryType == 1 (SCAN) |
BinaryObject | filter | byte | filterPlatform (when filter is not null)int | pageSize
int | partition (-1 for no partition) |
bool | local |
string | schema |
int | pageSize |
string | sql |
int | argument count |
n * Object | arguments |
bool | distributed joins |
bool | local |
bool | enforce join order |
bool | colocated |
bool | lazy |
long | timeout, in milliseconds |
Response | |
---|---|
long | continuousQueryId - used to retrieve initial query data and stop the query with OP_RESOURCE_CLOSE |
int | columnCount (when initial query is SQL) |
n * string | column names (when initial query is SQL) |
...
RESOURCE_CLOSE |
...
Note: AbstractContinuousQuery.autoUnsubscribe should be always true for thin client continuous queries.
As a result of OP_QUERY_CONTINUOUS and until OP_RESOURCE_CLOSE is called, client should expect OP_QUERY_CONTINUOUS_EVENT_NOTIFICATION messages from the server:
int | event count | ||||||||
n * CacheEntryEvent |
|
...
Jira | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|