REST Query Index Stage

• any HTTP or HTTPS request: <http-protocol>://<path>
• a Solr request: solr://COLLECTION_NAME/…​
• a Fusion service request: extservice://SERVICE_NAME/<path>

• POJOs
• JSON
• XML

​

Call Parameters

1. In the uri, queryParams, headers, and entity values, replace each ${fieldName} with <first(doc.fieldName)>. For example, change ${url} to <first(doc.url)>. <first(...)> keeps the legacy behavior of using only the first value of a multi-valued field. For single-valued fields, <doc.fieldName> returns the same result. Don’t use ${doc.fieldName}. That syntax looks for a field literally named doc.fieldName, which is treated as a missing field.
2. Replace every ${...} reference in a value at the same time. If a value contains a ${...} reference, the stage doesn’t evaluate template expressions in that value.
3. Check how the stage should handle missing fields. With ${fieldName}, a missing field in uri skips the call, a missing field in queryParams or headers omits that entry, and a missing field in entity becomes an empty string. With template expressions, a missing field becomes an empty string and the call still runs. To skip documents that don’t have the field, set the stage Condition to an expression such as doc.hasField("url").
4. Save the stage and confirm that the deprecation warning no longer appears in the logs.

"params" : {
  "uri" : "solr://collection1/select",
  "method" : "GET",
  "queryParams" : {
    "q" : "{!field f=a_txt v=$prodName}",
    "prodName" : "<doc.prodName>"
  }
}

​

Mapping Rules

• path. an XPath expression. It is assumed that this expression always returns a node list, and each returned node is processed separately and its converted value is added to a multi-valued field.
• target. the name of the target field in the current document where the value(s) will be stored.
• append. if true, values extracted from the RPC response will be appended to the target multi-valued field. When this is false, the default, existing values in the target field will be discarded and replaced with the values from the RPC response.
• xml. if true, the extracted DOM nodes will be separately serialized to XML and the resulting XML-formatted text will be added to the target field. When this is false, the default, the extracted DOM nodes will be flattened and converted to a list of fields. Field names in this case will correspond to XML element names, dot-separated, and element attributes will be represented as fields with @attributeName suffix.

​

Examples

{
  "type" : "indexing-rpc",
  "id" : "BasicSolrCall",
  "mappingRules" : [ {
    "path" : "//result/doc[1]/str[@name='foo_s']/text()",
    "target" : "foo_s",
    "append" : true,
    "xml" : false
  }, {
    "path" : "//result/doc/arr[@name='a_txt']/*",
    "target" : "doc_txt",
    "append" : true,
    "xml" : false
  } ],
  "debug" : true,
  "params" : {
    "uri" : "solr://collection1/select",
    "method" : "GET",
    "queryParams" : {
      "q" : "a_txt:<doc.doc_value>"
    },
    "headers" : { }
  },
  "skip" : false,
  "label" : "indexing-rpc"
}

{
  "type" : "indexing-rpc",
  "id" : "demo",
  "debug" : true,
  "params" : {
    "uri" : "http://FUSION_HOST:FUSION_PORT/api/stopwords/movies",
    "method" : "PUT",
    "headers" : { "Content-Type" : "application/json" },
    "entity" : "New stopword list"
  },
  "skip" : false,
  "label" : "Indexing RPC Demo",
  "type" : "indexing-rpc"
}

​

Configuration