Hi, Alan:
Please work with your support representative to create a ticket to investigate
the issue.
You might experiment with a custom constraint to see whether that comes closer
to what you need.
Alternatively, you might find that cts:parse() provides a faster solution than
search:parse()
We’ve noticed that when using a Field constraint with the Search API, that
search strings such as:
KW:(war peace)
are parsed in such a way that the two words are treated as a phrase. The
resulting query looks like this:
(cts:search(/book, cts:field-word-query("keywords", "war peace",
