You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@lucene.apache.org by Paul Taylor <pa...@fastmail.fm> on 2015/03/05 14:25:12 UTC
is this lucene 4.1.0 bug in PerFieldPostingsFormat
Hi
Is this a Lucene (4.1.0) (known) bug or application code error, (I don't
have details of the search just this stacktrace) I'm assuming bug
because user code is just passing a search to Lucene, but I cant find
anything in JIRA
|java.lang.NullPointerException
at java.util.TreeMap.getEntry(TreeMap.java:342)
at java.util.TreeMap.get(TreeMap.java:273)
at org.apache.lucene.codecs.perfield.PerFieldPostingsFormat$FieldsReader.terms(PerFieldPostingsFormat.java:215)
at org.apache.lucene.search.TermCollectingRewrite.collectTerms(TermCollectingRewrite.java:58)
at org.apache.lucene.search.ConstantScoreAutoRewrite.rewrite(ConstantScoreAutoRewrite.java:95)
at org.apache.lucene.search.MultiTermQuery$ConstantScoreAutoRewrite.rewrite(MultiTermQuery.java:220)
at org.apache.lucene.search.MultiTermQuery.rewrite(MultiTermQuery.java:286)
at org.apache.lucene.search.BooleanQuery.rewrite(BooleanQuery.java:429)
at org.apache.lucene.search.IndexSearcher.rewrite(IndexSearcher.java:616)
at org.apache.lucene.search.IndexSearcher.createNormalizedWeight(IndexSearcher.java:663)
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:281)
at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:269)
at org.musicbrainz.search.servlet.AbstractSearchServer.search(AbstractSearchServer.java:190)
at org.musicbrainz.search.servlet.AbstractSearchServer.search(AbstractSearchServer.java:172)
at org.musicbrainz.search.servlet.SearchServerServlet.doSearch(SearchServerServlet.java:616)
at org.musicbrainz.search.servlet.SearchServerServlet.doGet(SearchServerServlet.java:551)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
thanks Paul
|
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 06/03/2015 17:34, Michael McCandless wrote:
> On Fri, Mar 6, 2015 at 11:03 AM, Paul Taylor <pa...@fastmail.fm> wrote:
>
>> Right, did you see my last post the query parser does trap the exception if
>> you enable assertions. I thought this was what you were saying was fixed in
>> a later version, but assume you actually mean search is fixed not parser
> Well it's both: Lucene should catch illegal null to all its Query
> classes, and Robert opened
> https://issues.apache.org/jira/browse/LUCENE-6345 for that.
>
> And then no query parser should ever send an invalid null down to
> Lucene queries ... that's the bug/test I think you should open?
Ok Ive done it with test case , I think at least the starting issue is
specific to MultiFieldQueryParser
https://issues.apache.org/jira/browse/LUCENE-6347
>> Is SimpleQueryParser identical to ClassicQueryParser without regular
>> expressions, or not ?
> It's completely different. It's goals are to support only the common
> reasonable-performing queries and do it's best-effort to make a query
> even on invalid input (not throw a ParseException).
Right I cant change the query syntax of a live system, although a way to
disable just regualr expressions would be good as we dont officiallly
support that.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Fri, Mar 6, 2015 at 11:03 AM, Paul Taylor <pa...@fastmail.fm> wrote:
> Right, did you see my last post the query parser does trap the exception if
> you enable assertions. I thought this was what you were saying was fixed in
> a later version, but assume you actually mean search is fixed not parser
Well it's both: Lucene should catch illegal null to all its Query
classes, and Robert opened
https://issues.apache.org/jira/browse/LUCENE-6345 for that.
And then no query parser should ever send an invalid null down to
Lucene queries ... that's the bug/test I think you should open?
> Is SimpleQueryParser identical to ClassicQueryParser without regular
> expressions, or not ?
It's completely different. It's goals are to support only the common
reasonable-performing queries and do it's best-effort to make a query
even on invalid input (not throw a ParseException).
See https://issues.apache.org/jira/browse/LUCENE-5336
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 06/03/2015 15:07, Michael McCandless wrote:
> On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor <pa...@fastmail.fm> wrote:
>> On 05/03/2015 19:01, Michael McCandless wrote:
>>> On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor <pa...@fastmail.fm>
>>> wrote:
>>>> On 05/03/2015 15:53, Paul Taylor wrote:
>>>>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>>>> It looks like field was null?
>>>>>>
>>>>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>>>>> a real check.
>>>>>>
>>>>>> Mike McCandless
>>>>> Hi, thankyou Il try and get the query logged for when it next happens
>>>> Okay here are two lucene queries that cause the issue
>>>>
>>>> artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
>>>>
>>>> artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg
>>>> Edit)
>>>>
>>>>
>>>> So I think the problem is that the users are not aware of the regular
>>>> expression syntax, escaping or removing the slashes and it works
>>>>
>>>> (Interestingly just removing one of the slashes
>>>>
>>>> artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
>>>>
>>>> gives me the ParseException instead of the NullPointerException
>>>> )
>>> Which query parser are you using? Seems like a bug if that query
>>> parser can do this ...
>> ClassicQueryParser, but the point is that we provide a webservice that allow
>> users to use the full query syntax as it would be impossible to second guess
>> what the user may want to do so I dont there is a bug in the queryparser in
>> that that way. We just receive a text string that we send to Lucene, I
>> would hope if the syntax was incorrect Lucene would just give a
>> ParseException
> Well I think that means there is a bug in the query parser?
>
> I.e. it should throw a ParseException, not pass a null field value
> down to Lucene, when this query text is passed to it.
>
> Or it should set the field to a non-null value (not sure why it
> doesn't use the default field name for the RegexpQuery).
Right, did you see my last post the query parser does trap the exception
if you enable assertions. I thought this was what you were saying was
fixed in a later version, but assume you actually mean search is fixed
not parser
>
>>>> But how can I fix this at my end so that Lucene returns an ParseException
>>>> rather than NullPointerException ?
>>> We need to fix the query parser.
>>>
>>>> Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
>>> Sorry I don't offhand ... though the fix is to throw
>>> IllegalArgumentException instead of NPE.
>> Why not ParseException ?
>>> Why not just upgrade to the latest bugfix (4.10.4)?
>>>
>> In the past Ive generally tried to use the latest version of Lucene, but
>> there are usually at least some changes required even updating minor
>> versions. So expect 4.10.4 will give me more issues, and if its going to
>> throw IllegalArgumentException rather than ParseExeption not sure that
>> helpful.
> Can you open a Jira issue and put a test case up?
Okay, yes if this is new issue, just waiting for confirmation from you.
> You could also try switching to the new "SimpleQueryParser": it does
> not even produce RegexpQuery. It's quite dangerous to let users make
> arbitrary regexps ...
>
Is SimpleQueryParser identical to ClassicQueryParser without regular
expressions, or not ?
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <ij...@fastmail.fm>.
On 06/03/2015 15:07, Michael McCandless wrote:
> On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor <pa...@fastmail.fm> wrote:
>> On 05/03/2015 19:01, Michael McCandless wrote:
>>> On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor <pa...@fastmail.fm>
>>> wrote:
>>>> On 05/03/2015 15:53, Paul Taylor wrote:
>>>>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>>>> It looks like field was null?
>>>>>>
>>>>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>>>>> a real check.
>>>>>>
>>>>>> Mike McCandless
>>>>> Hi, thankyou Il try and get the query logged for when it next happens
>>>> Okay here are two lucene queries that cause the issue
>>>>
>>>> artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
>>>>
>>>> artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg
>>>> Edit)
>>>>
>>>>
>>>> So I think the problem is that the users are not aware of the regular
>>>> expression syntax, escaping or removing the slashes and it works
>>>>
>>>> (Interestingly just removing one of the slashes
>>>>
>>>> artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
>>>>
>>>> gives me the ParseException instead of the NullPointerException
>>>> )
>>> Which query parser are you using? Seems like a bug if that query
>>> parser can do this ...
>> ClassicQueryParser, but the point is that we provide a webservice that allow
>> users to use the full query syntax as it would be impossible to second guess
>> what the user may want to do so I dont there is a bug in the queryparser in
>> that that way. We just receive a text string that we send to Lucene, I
>> would hope if the syntax was incorrect Lucene would just give a
>> ParseException
> Well I think that means there is a bug in the query parser?
>
> I.e. it should throw a ParseException, not pass a null field value
> down to Lucene, when this query text is passed to it.
>
> Or it should set the field to a non-null value (not sure why it
> doesn't use the default field name for the RegexpQuery).
Right, did you see my last post the query parser does trap the exception
if you enable assertions. I thought this was what you were saying was
fixed in a later version, but assume you actually mean search is fixed
not parser
>>>> But how can I fix this at my end so that Lucene returns an ParseException
>>>> rather than NullPointerException ?
>>> We need to fix the query parser.
>>>
>>>> Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
>>> Sorry I don't offhand ... though the fix is to throw
>>> IllegalArgumentException instead of NPE.
>> Why not ParseException ?
>>> Why not just upgrade to the latest bugfix (4.10.4)?
>>>
>> In the past Ive generally tried to use the latest version of Lucene, but
>> there are usually at least some changes required even updating minor
>> versions. So expect 4.10.4 will give me more issues, and if its going to
>> throw IllegalArgumentException rather than ParseExeption not sure that
>> helpful.
> Can you open a Jira issue and put a test case up?
Okay, yes if this is new issue, just waiting for confirmation from you.
> You could also try switching to the new "SimpleQueryParser": it does
> not even produce RegexpQuery. It's quite dangerous to let users make
> arbitrary regexps ...
>
Is SimpleQueryParser identical to ClassicQueryParser without regular
expressions, or not ?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Thu, Mar 5, 2015 at 4:27 PM, Paul Taylor <pa...@fastmail.fm> wrote:
> On 05/03/2015 19:01, Michael McCandless wrote:
>>
>> On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor <pa...@fastmail.fm>
>> wrote:
>>>
>>> On 05/03/2015 15:53, Paul Taylor wrote:
>>>>
>>>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>>>
>>>>> It looks like field was null?
>>>>>
>>>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>>>> a real check.
>>>>>
>>>>> Mike McCandless
>>>>
>>>> Hi, thankyou Il try and get the query logged for when it next happens
>>>
>>> Okay here are two lucene queries that cause the issue
>>>
>>> artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
>>>
>>> artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg
>>> Edit)
>>>
>>>
>>> So I think the problem is that the users are not aware of the regular
>>> expression syntax, escaping or removing the slashes and it works
>>>
>>> (Interestingly just removing one of the slashes
>>>
>>> artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
>>>
>>> gives me the ParseException instead of the NullPointerException
>>> )
>>
>> Which query parser are you using? Seems like a bug if that query
>> parser can do this ...
>
> ClassicQueryParser, but the point is that we provide a webservice that allow
> users to use the full query syntax as it would be impossible to second guess
> what the user may want to do so I dont there is a bug in the queryparser in
> that that way. We just receive a text string that we send to Lucene, I
> would hope if the syntax was incorrect Lucene would just give a
> ParseException
Well I think that means there is a bug in the query parser?
I.e. it should throw a ParseException, not pass a null field value
down to Lucene, when this query text is passed to it.
Or it should set the field to a non-null value (not sure why it
doesn't use the default field name for the RegexpQuery).
>>> But how can I fix this at my end so that Lucene returns an ParseException
>>> rather than NullPointerException ?
>>
>> We need to fix the query parser.
>>
>>> Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
>>
>> Sorry I don't offhand ... though the fix is to throw
>> IllegalArgumentException instead of NPE.
>
> Why not ParseException ?
>>
>> Why not just upgrade to the latest bugfix (4.10.4)?
>>
> In the past Ive generally tried to use the latest version of Lucene, but
> there are usually at least some changes required even updating minor
> versions. So expect 4.10.4 will give me more issues, and if its going to
> throw IllegalArgumentException rather than ParseExeption not sure that
> helpful.
Can you open a Jira issue and put a test case up?
You could also try switching to the new "SimpleQueryParser": it does
not even produce RegexpQuery. It's quite dangerous to let users make
arbitrary regexps ...
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 05/03/2015 21:27, Paul Taylor wrote:
FWIW if I do enable assertions then parse does throw an assertion before
actually trying to do the search.
java.lang.AssertionError
at
org.apache.lucene.search.MultiTermQuery.<init>(MultiTermQuery.java:252)
at
org.apache.lucene.search.AutomatonQuery.<init>(AutomatonQuery.java:65)
at org.apache.lucene.search.RegexpQuery.<init>(RegexpQuery.java:90)
at org.apache.lucene.search.RegexpQuery.<init>(RegexpQuery.java:79)
at org.apache.lucene.search.RegexpQuery.<init>(RegexpQuery.java:69)
at
org.apache.lucene.queryparser.classic.QueryParserBase.newRegexpQuery(QueryParserBase.java:790)
at
org.apache.lucene.queryparser.classic.QueryParserBase.getRegexpQuery(QueryParserBase.java:1005)
at
org.apache.lucene.queryparser.classic.QueryParserBase.handleBareTokenQuery(QueryParserBase.java:1075)
at
org.apache.lucene.queryparser.classic.QueryParser.Term(QueryParser.java:359)
at
org.apache.lucene.queryparser.classic.QueryParser.Clause(QueryParser.java:258)
at
org.apache.lucene.queryparser.classic.QueryParser.Query(QueryParser.java:213)
at
org.apache.lucene.queryparser.classic.QueryParser.TopLevelQuery(QueryParser.java:171)
at
org.apache.lucene.queryparser.classic.QueryParserBase.parse(QueryParserBase.java:120)
at
org.musicbrainz.search.servlet.AbstractSearchServer.parseQuery(AbstractSearchServer.java:208)
But in production its not usual/good idea to enable assertions.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 05/03/2015 19:01, Michael McCandless wrote:
> On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor <pa...@fastmail.fm> wrote:
>> On 05/03/2015 15:53, Paul Taylor wrote:
>>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>> It looks like field was null?
>>>>
>>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>>> a real check.
>>>>
>>>> Mike McCandless
>>> Hi, thankyou Il try and get the query logged for when it next happens
>> Okay here are two lucene queries that cause the issue
>>
>> artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
>>
>> artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg Edit)
>>
>>
>> So I think the problem is that the users are not aware of the regular
>> expression syntax, escaping or removing the slashes and it works
>>
>> (Interestingly just removing one of the slashes
>>
>> artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
>>
>> gives me the ParseException instead of the NullPointerException
>> )
> Which query parser are you using? Seems like a bug if that query
> parser can do this ...
ClassicQueryParser, but the point is that we provide a webservice that
allow users to use the full query syntax as it would be impossible to
second guess what the user may want to do so I dont there is a bug in
the queryparser in that that way. We just receive a text string that we
send to Lucene, I would hope if the syntax was incorrect Lucene would
just give a ParseException
>> But how can I fix this at my end so that Lucene returns an ParseException
>> rather than NullPointerException ?
> We need to fix the query parser.
>
>> Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
> Sorry I don't offhand ... though the fix is to throw
> IllegalArgumentException instead of NPE.
Why not ParseException ?
> Why not just upgrade to the latest bugfix (4.10.4)?
>
In the past Ive generally tried to use the latest version of Lucene, but
there are usually at least some changes required even updating minor
versions. So expect 4.10.4 will give me more issues, and if its going
to throw IllegalArgumentException rather than ParseExeption not sure
that helpful.
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Michael McCandless <lu...@mikemccandless.com>.
On Thu, Mar 5, 2015 at 12:12 PM, Paul Taylor <pa...@fastmail.fm> wrote:
> On 05/03/2015 15:53, Paul Taylor wrote:
>>
>> On 05/03/2015 14:43, Michael McCandless wrote:
>>>
>>> It looks like field was null?
>>>
>>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>>> a real check.
>>>
>>> Mike McCandless
>>
>> Hi, thankyou Il try and get the query logged for when it next happens
>
> Okay here are two lucene queries that cause the issue
>
> artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
>
> artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg Edit)
>
>
> So I think the problem is that the users are not aware of the regular
> expression syntax, escaping or removing the slashes and it works
>
> (Interestingly just removing one of the slashes
>
> artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
>
> gives me the ParseException instead of the NullPointerException
> )
Which query parser are you using? Seems like a bug if that query
parser can do this ...
> But how can I fix this at my end so that Lucene returns an ParseException
> rather than NullPointerException ?
We need to fix the query parser.
> Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
Sorry I don't offhand ... though the fix is to throw
IllegalArgumentException instead of NPE.
Why not just upgrade to the latest bugfix (4.10.4)?
Mike McCandless
http://blog.mikemccandless.com
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 05/03/2015 15:53, Paul Taylor wrote:
> On 05/03/2015 14:43, Michael McCandless wrote:
>> It looks like field was null?
>>
>> Back in 4.1.0 we just assert field != null, but in newer releases it's
>> a real check.
>>
>> Mike McCandless
> Hi, thankyou Il try and get the query logged for when it next happens
Okay here are two lucene queries that cause the issue
artist:pandora /reyli barba recording:Solo el y yo/Alguien llena mi lugar
artist:Jeremih recording:Rated R (The Masterpiece) (Bear//Face Bootleg Edit)
So I think the problem is that the users are not aware of the regular expression syntax, escaping or removing the slashes and it works
(Interestingly just removing one of the slashes
artist:pandora /reyli barba recording:Solo el y yo Alguien llena mi lugar
gives me the ParseException instead of the NullPointerException
)
But how can I fix this at my end so that Lucene returns an ParseException rather than NullPointerException ?
Do you know the earliest verion of Lucene after 4.1.0 to handle this ?
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Paul Taylor <pa...@fastmail.fm>.
On 05/03/2015 14:43, Michael McCandless wrote:
> It looks like field was null?
>
> Back in 4.1.0 we just assert field != null, but in newer releases it's
> a real check.
>
> Mike McCandless
Hi, thankyou Il try and get the query logged for when it next happens
Paul
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org
Re: is this lucene 4.1.0 bug in PerFieldPostingsFormat
Posted by Michael McCandless <lu...@mikemccandless.com>.
It looks like field was null?
Back in 4.1.0 we just assert field != null, but in newer releases it's
a real check.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Mar 5, 2015 at 8:25 AM, Paul Taylor <pa...@fastmail.fm> wrote:
> Hi
>
> Is this a Lucene (4.1.0) (known) bug or application code error, (I don't
> have details of the search just this stacktrace) I'm assuming bug because
> user code is just passing a search to Lucene, but I cant find anything in
> JIRA
>
> |java.lang.NullPointerException
> at java.util.TreeMap.getEntry(TreeMap.java:342)
> at java.util.TreeMap.get(TreeMap.java:273)
> at
> org.apache.lucene.codecs.perfield.PerFieldPostingsFormat$FieldsReader.terms(PerFieldPostingsFormat.java:215)
> at
> org.apache.lucene.search.TermCollectingRewrite.collectTerms(TermCollectingRewrite.java:58)
> at
> org.apache.lucene.search.ConstantScoreAutoRewrite.rewrite(ConstantScoreAutoRewrite.java:95)
> at
> org.apache.lucene.search.MultiTermQuery$ConstantScoreAutoRewrite.rewrite(MultiTermQuery.java:220)
> at org.apache.lucene.search.MultiTermQuery.rewrite(MultiTermQuery.java:286)
> at org.apache.lucene.search.BooleanQuery.rewrite(BooleanQuery.java:429)
> at org.apache.lucene.search.IndexSearcher.rewrite(IndexSearcher.java:616)
> at
> org.apache.lucene.search.IndexSearcher.createNormalizedWeight(IndexSearcher.java:663)
> at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:281)
> at org.apache.lucene.search.IndexSearcher.search(IndexSearcher.java:269)
> at
> org.musicbrainz.search.servlet.AbstractSearchServer.search(AbstractSearchServer.java:190)
> at
> org.musicbrainz.search.servlet.AbstractSearchServer.search(AbstractSearchServer.java:172)
> at
> org.musicbrainz.search.servlet.SearchServerServlet.doSearch(SearchServerServlet.java:616)
> at
> org.musicbrainz.search.servlet.SearchServerServlet.doGet(SearchServerServlet.java:551)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:618)
> thanks Paul
> |
>
---------------------------------------------------------------------
To unsubscribe, e-mail: java-user-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-user-help@lucene.apache.org