Re: null Query from MultiFieldQueryParser.getFieldQuery

Nachricht- > Von: Steve Rowe [mailto:sar...@gmail.com] > Gesendet: Freitag, 30. September 2016 21:48 > An: java-user@lucene.apache.org > Cc: Oliver Kaleske > Betreff: Re: null Query from MultiFieldQueryParser.getFieldQuery > > Hi Oliver, > > Thanks for reporting

Re: null Query from MultiFieldQueryParser.getFieldQuery

: Steve Rowe [mailto:sar...@gmail.com] Gesendet: Freitag, 30. September 2016 21:48 An: java-user@lucene.apache.org Cc: Oliver Kaleske Betreff: Re: null Query from MultiFieldQueryParser.getFieldQuery Hi Oliver, Thanks for reporting and for the analysis, this is a bug. See <https://issues.apache.

Re: null Query from MultiFieldQueryParser.getFieldQuery

Hi Oliver, Thanks for reporting and for the analysis, this is a bug. See , where I’ve put up a patch with a fix that treats all non-BooleanQuery queries opaquely (like TermQuery), and adds a test for the SynonymQuery case that fails without the

Re: null Query from MultiFieldQueryParser.getFieldQuery

I'm not very familiar with this part of the code base so I could easily overlook something. Maybe you can open a JIRA and attach a minimal test case that reproduces the issue? Le lun. 19 sept. 2016 à 13:48, Oliver Kaleske a écrit : > Hi, > > in updating Lucene from 6.1.0 to 6.2.0 I came across t

null Query from MultiFieldQueryParser.getFieldQuery

Hi, in updating Lucene from 6.1.0 to 6.2.0 I came across the following: We have a subclass of MultiFieldQueryParser (MFQP) for creating a custom type of Query, which calls getFieldQuery() on its base class (MFQP). For each of its search fields, this method has a Query created by calling getFiel