[SOLR-14913] Including non-existing field in edismax field alias breaks parsing of boolean query

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 7.6, 8.6.2
• Component/s: query parsers
• Assignee: Unassigned
• Reporter: Johannes Baiter
• Created: 05/Oct/20 15:58
• Updated: 09/Oct/20 15:51

Description

When including a non-existing field in a f.<alias>.qf field alias, boolean queries are parsed incorrectly.
For non-boolean queries the invalid field is simply ignored, but in boolean queries only the first search term is resolved to the fields from the alias, while the second term is resolved to the text field.
This parse is identical to the parse obtained from the same query with brackets removed, i.e. <alias>: (<termA> <termB>) returns the exact same parse as <alias>:<termA> <termB>.

I was able to reproduce this with the demo index in the latest Docker setup:

$ docker run --name solr_demo -d -p 8983:8983 solr:8 solr-demo

Query:

$ curl "http://localhost:8983/solr/demo/select?\
debugQuery=on\
&defType=edismax\
&f.meta.qf=name+manu+cat+features+idontexist\
&q=meta%3A%28samsung+noiseguard%29"

Expected Parse:

{ "debug":
  { "parsedquery_toString": "+((name:samsung | manu:samsung | features:samsung | cat:samsung)) (name:noiseguard | manu:noiseguard | features: noiseguard | cat:noiseguard))" }
}

Actual Parse:

{ "debug":
  { "parsedquery_toString": "+((name:samsung | manu:samsung | features:samsung | cat:samsung) (_text_:noiseguard))" }
}