I can reproduce this with a unit test - will post to JIRA shortly.
Peter
On Fri, Oct 16, 2009 at 8:06 AM, Peter Keegan wrote:
> next() is called in PayloadNearQuery->setFreqCurrentDoc:
> super.setFreqCurrentDoc();
> But, I think it should be called before 'getPayloads'. That doesn't fix the
> NPE
next() is called in PayloadNearQuery->setFreqCurrentDoc:
super.setFreqCurrentDoc();
But, I think it should be called before 'getPayloads'. That doesn't fix the
NPE, though.
The empty PQ occurs in the outermost span in the query, and seems to fail on
the last document it scores.
Prior to 2.9, I'd be
And, you don't get this on 2.4.1?
Are you sure you've called next()? Is it by chance on the first
document it tries to score that it fails?
-Grant
On Oct 15, 2009, at 1:28 PM, Peter Keegan wrote:
The query is:
+payloadNear([spanNear([contents:insurance, contents:agent], 1,
false),
The query is:
+payloadNear([spanNear([contents:insurance, contents:agent], 1, false),
spanNear([contents:winston, contents:salem], 1, false)], 10, false)
It's using the default payload function scorer (average value)
It doesn't happen on all queries of this type, only a handful. This is
pr
Are you using any custom query types? Anything to help us reproduce
(like the acutal query this happened on) would be greatly appreciated.
-Yonik
http://www.lucidimagination.com
On Thu, Oct 15, 2009 at 1:17 PM, Peter Keegan wrote:
> I'm using Lucene 2.9 and sometimes get a NPE in NearSpansUnor
