Skip to main content
The Milvus Response Update stage updates response documents with vectors similarity and ensemble scores (see Milvus documentation). It should be used after the Milvus Ensemble Query stage and after the Solr Query stage.
DeprecatedThis stage is deprecated in Fusion 5.9.5 and later. It will be removed in a future release.Replace the Milvus Response Update Query Stage with Seldon or Lucidworks AI vector query stages. These alternatives improve performance when updating response documents with vector similarity data.

​
Query pipeline stage condition examples

Stages can be triggered conditionally when a script in the Condition field evaluates to true. Some examples are shown below. Run this stage only for mobile clients: 
params.deviceType === "mobile"
Run this stage when debugging is enabled: 
params.debug === "true"
Run this stage when the query includes a specific term: 
params.q && params.q.includes("sale")
Run this stage when multiple conditions are met: 
request.hasParam("fusion-user-name") && request.getFirstParam("fusion-user-name").equals("SuperUser");
!request.hasParam("isFusionPluginQuery")
The first condition checks that the request parameter “fusion-user-name” is present and has the value “SuperUser”. The second condition checks that the request parameter “isFusionPluginQuery” is not present.

​
Configuration

When entering configuration values in the UI, use unescaped characters, such as \t for the tab character. When entering configuration values in the API, use escaped characters, such as \\t for the tab character.