Limitations
The following constraints must be considered when defining a real-time alert:
-
It takes only transformed UQL into account:
It means that refinements (i.e. facets) are not managed. An alert is published when a new document matches the query regardless of other refinements. You may use prefix handlers instead to restrict the query.
-
Some UQL operators are not supported:
-
Geo operators:
distance,within. -
Separators:
#sentence,#paragraph,#page -
Attributes:
#uid,#around -
Other operators:
INNERJOIN,FUZZYAND,SPLIT,XOR,BUTNOT -
Queries with both proximity and boolean operators. For example,
(cat OR cats) NEAR (dog OR dogs)
-
-
It is triggered at the end of the analysis pipeline, before semantic processing and mapping.
It means that the following objects are not managed:
-
Metas stored in a dynamic field or renamed during mapping.
-
Filters based on virtual expressions.
-
Conditions set on entities built during the semantic processing (for example, named entities or related terms).
-
Categories (for example,
Top/Language/fr).A workaround is to set a meta with the value of the meta you need to retrieve, directly in the analysis pipeline and before the Real-time alerting processor.
-