Thanks Matteo, looks like you found a bug. I can reproduce this with simpler queries too:
_query_:"ABC" name_t:"white cat"~3 is parsed to text:abc name_t:"white cat" Can you open a JIRA for this? -Yonik On Mon, May 16, 2016 at 10:23 AM, Matteo Grolla <matteo.gro...@gmail.com> wrote: > Hi everyone, > I have a problem with nested queries > If the order is: > 1) query > 2) nested query (embedded in _query_:"...") > everything works fine > if it is the opposite, like this > > http://localhost:8983/solr/test/select?q=_query_:%22{!lucene%20df=name_t}(\%22black%20dog\%22)%22%20OR%20name_t:%22white%20cat%22~20&debug=true > > then the span query "white cat"~20 > becomes a phrase query "white cat" > > if both queries are embedded in _query_:"..." the behaviour is correct. > The bevaviour seems odd to me, is there any reason for it? > > <response> > <lst name="responseHeader"> > <int name="status">0</int> > <int name="QTime">8</int> > <lst name="params"> > <str name="q"> > _query_:"{!lucene df=name_t}(\"black dog\")" OR name_t:"white cat"~20 > </str> > <str name="debug">true</str> > </lst> > </lst> > <result name="response" numFound="0" start="0"/> > <lst name="debug"> > <str name="rawquerystring"> > _query_:"{!lucene df=name_t}(\"black dog\")" OR name_t:"white cat"~20 > </str> > <str name="querystring"> > _query_:"{!lucene df=name_t}(\"black dog\")" OR name_t:"white cat"~20 > </str> > <str name="parsedquery"> > PhraseQuery(name_t:"black dog") PhraseQuery(name_t:"white cat") > </str> > <str name="parsedquery_toString">name_t:"black dog" name_t:"white cat"</str> > <lst name="explain"/> > <str name="QParser">LuceneQParser</str>
