Thanks Will. We’ll look into the different parse options.
Alan
> On Mar 2, 2018, at 1:56 PM, Will Thompson wrote:
>
> Alan,
>
> It appears the behavior of search:parse() and cts:parse() are different in
> this respect. cts:parse() uses the individual word tokens in the query, the
> equiva
Alan,
It appears the behavior of search:parse() and cts:parse() are different in this
respect. cts:parse() uses the individual word tokens in the query, the
equivalent of an ORing them:
cts:parse('by:(twain frost)',
map:new(map:entry("by", cts:element-reference(xs:QName("name")
=> cts:e
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() fo
