[SOLR-3261] edismax ignores explicit operators when literal colon is found

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.6, 4.0-ALPHA
• Component/s: query parsers
• Assignee: Juan Grande
• Reporter: Chris M. Hostetter
• Created: 20/Mar/12 21:38
• Updated: 10/May/13 10:40
• Resolved: 27/Mar/12 23:41

Description

Using the 3.5 example this query...

q = bogus:xxx AND text_t:yak
http://localhost:8983/solr/select/?debugQuery=true&qf=a_t+b_t&defType=edismax&mm=0&q=bogus:xxx+AND+text_t:yak

parses as...

+(DisjunctionMaxQuery((a_t:bogus:xxx | b_t:bogus:xxx)) DisjunctionMaxQuery((a_t:and | b_t:and)) text_t:yak)

(Note that "AND" is considered a term and is searched for in the qf fields)

But this query...
q = foo_s:xxx AND text_t:yak
http://localhost:8983/solr/select/?debugQuery=true&qf=a_t+b_t&defType=edismax&mm=0&q=foo_s:xxx+AND+text_t:yak

parses correctly treating AND as an explicit operator...

+(+foo_s:xxx +text_t:yak)

(this problem also seems to affect trunk circa 2012-03-20)

Issue Links

• is part of: SOLR-2368 Improve extended dismax (edismax) parser
• is related to: SOLR-2959 edismax uf param does not work with magic fields '_query_' and '_val_'