Template expressions are a way to map field values in a document. They are used to configure some Fusion index pipeline stages, query pipeline stages, and messaging services. When the value of a configuration parameter is a template expression, that expression is dynamically evaluated at runtime by the StringTemplate library. Fusion template expressions are delimited by angle bracket charactersDocumentation Index
Fetch the complete documentation index at: https://doc.lucidworks.com/llms.txt
Use this file to discover all available pages before exploring further.
< and >.
The expression consists of the name of a variable in the scope of that component.
Since these variables are Java objects, if object foo of type Foo has a field named bar, the expression <foo.bar> will evaluate to the string representation of the contents of field bar.
For example, given a PipelineDocument where a field named title has a value of Star Wars, the template expression <doc.title> evaluates to Star Wars.
Index pipeline stage template expression variables
Index stages have the following variables available:ctx. Context: used to pass variables between stagesdoc. PipelineDocument: Fusion internal representation of a Solr Document. Please note that if you change this class in ways that affect the serialized form (adding fields, for example) you need to change the deserialization code inGenericJSONDocumentMessageReader.
<request.q>.
Query pipeline stage template expression variables
Query stages have the following variables available:ctx. Context: used to pass variables between stagesreqResp. QueryRequestAndResponse: deserializes pre-request parameters and makes them available
<request.q>.
Example
Check that a query has anfq filter on a given field for a given value:
In the UI, set property name to ids and Property Value to req.hasParam("fq")
Messaging services template expression variables
Messages have a set of variables which correspond to the parts of a system message:- id
- to
- from
- subject
- body
- type
- schedule