Check the function in your search options node, and ensure that the function named in the error message has been defined. You may need to specify a namespace (@ns) and file path (@at) if the function is an extension located in a custom XQuery module, or a user-defined function (@udf) if the function is a user-defined aggregate function.
Implementation of a custom constraint requires implementation of a parsing function. A custom constraint has been specified, but the configuration is incorrect or does not refer to a parsing function.
Check your search options node with search:check-options to ensure it is valid. Validate that the custom library module is available at the expected path, and that the namespace and local name correctly refer to a function in that module.
Check your search options node with search:check-options in strict mode to identify the missing index.
A custom constraint expected to resolve facets (
@facet = "true") must supply code to implement, at minimum, a finish-facet function. Optionally, it may supply a
start-facet function to support concurrent facet resolution. This error indicates that the
finish-facet function has not been supplied, or that the options node configuring the custom constraint is incorrect.
If the constraint should not resolve facets, set
@facet ="false". If it should resolve facets, run search:check-options on the options node to ensure the configuration is valid.
The options supplied to this function must refer to a valid index configuration (collection, uri, range, field, or geospatial). Run search:check-options on the options node to ensure that the configuration is valid.
The Search API adds annotations as it parses queries in order to support round-tripping (search:parse generates an annotated parsed query while search:unparse takes an annotated parsed query and generates a string). The parse/unparse cycle is also used in other areas of the API, including search:remove-constraint. This error indicates that the parsed query cannot be reversed due to missing annotations. It is usually encountered when custom parsing code has been added to extend the API.
Add annotations to any custom parsing code. Consult documentation on customization of the Search API, or use search:parse to generate parsed queries and observe the annotation pattern. Contact support if further assistance is needed.
Anchors indicating a fixed point in time may be supplied for computed buckets, which allow for dynamic calculation of relative bucket boundaries on
dateTime constraints (e.g., compute bucket boundaries relative to "now"). This error indicates that the constraint type is inappropriate for the anchor.
Run search:check-options to validate the structure of the search options node. Check dynamic buckets.