I'm seeing some bizarre behavior (using folding feature if that matters), where aq filters are sometimes failing unless they are placed along with q
I have a single document that:
does not have the word "repair" in it but does contain words "service" and "offering"
satisfies this filter: @ftecz32xworkz32xplans45666=(d4582efd1c7642388975eac48dd4184a)
also satisfies @syssource==("Coveo_web_index XXXXXX")
(just don't want to post full index name)
For example:
1) suppose I have:
q:
aq: @ftecz32xworkz32xplans45666=(d4582efd1c7642388975eac48dd4184a)
@syssource==("Coveo_web_index XXXXXX")
this returns me 1 record as expected, and I see it comes from Coveo_web
2) but,
q: "repair"
aq: @ftecz32xworkz32xplans45666=(d4582efd1c7642388975eac48dd4184a)
@syssource==("Coveo_web_index XXXXXX")
I get 2 records, both of which come from Coveo_master ????
3) then, if I do:
q: repair @syssource==("Coveo_web_index XXXXXX")
aq: @ftecz32xworkz32xplans45666=(d4582efd1c7642388975eac48dd4184a)
I get 0 results (which is actually what I expected).
4)
q: service OR offering OR repair
aq:@syssource==("Coveo_web_index XXXXXX")
@ftecz32xworkz32xplans45666=(d4582efd1c7642388975eac48dd4184a)
I get 1 result
So why is example #2 behaving this way? I'd rather not have to use #2 as a workaround...am I missing something? Thanks
Answer by Martin Laporte · Oct 18, 2016 at 03:19 AM
q
and aq
are combined together using an AND
operator, so it's indeed weird that #2 yields two results. One thing that might produce surprising results such as this is if "partial matching" is enabled. When on, it applies some special processing on q
, and with the proper parameters it can cause documents to match without containing the keyword.
Since partial match is automatically disabled if you include field expressions in q
, that would explain why #3 returns 0 results.
Otherwise, if you load the search page with debug=1
in the query string and then check the REST requests in the Network tab, you'll be able to see the final query expressions that are evaluated at the index level; maybe this would give you a hint of what's amiss...
After much todo we figured out it was Top Results that were coming back. We were a little surprised that even the @sysindex filter is ignored for top results.
Coveo REST API to create a Related Query Component 0 Answers
RankingInfo coming back as null or Total weight:0 0 Answers
Empty Search JSON result 1 Answer
coveo search API started and then stopped 1 Answer
coveo trends usage analytics API 1 Answer