Constants functions wrap constants so they can be used in filter functions. For example if a filter checks for
X = 10, you would first wrap
10 using
C_IntConstant().
The C_RuleFunction() function allows you to specify a rule function containing a custom filter condition.
Query functions take various actions for a specified entity or set of entities. For example,
C_CacheInvoke() allows you to invoke a rule function for all matching entities in the cache.
Tool tips in the user interface (and reproduced in the TIBCO BusinessEvents Functions Reference) explain how to use the functions singly or in combination to achieve the desired results.
The C_CacheOnlyMode*() functions are for use with entities that use cache-only cache mode.
The query optimization you set up is used by C_Query*() functions and by snapshot queries (available in TIBCO BusinessEvents Event Stream Processing add-on).
The snapshot query manager rewrites parts of the query’s where clause to use Coherence
IndexAwareFilters. Coherence, however, may or may not use the index, depending on how complex the filter is. Complex
where clauses containing function calls and joins will not be optimized. Only simple filters, such as
age > 60, or
name in (“a”, “b”, “c”), are re-written to use indexes.
You can set an index on an entity property in either of two ways: using a Coherence catalog function in your code, or setting a metadata property in the project’s Cluster Deployment Descriptor (CDD) file.
Using a Coherence Catalog Function You can define an index using the following function in your code:
property is the object Returned by the appropriate C_
DatatypeAtomGetter functions, for example,
C_StringAtomGetter().
isOrdered is a Boolean: set to true to order the contents of the indexed information, and set to false if you want to use an unordered index.
Using a Property Metadata Setting Do the following to create an unordered index on a property: