lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael McCandless (JIRA)" <>
Subject [jira] Updated: (LUCENE-1571) DistanceFilter problem with deleted documents
Date Sun, 14 Jun 2009 13:52:07 GMT


Michael McCandless updated LUCENE-1571:

    Attachment: LUCENE-1571.patch

OK I fixed it by switching to TermDocs(null), and also found another bug in the process (an
accidental leftover copy/paste {{i = bits.nextSetBit(i+1)}} in the non-chained case).  I also
fixed the chained case to avoid deleted docs.  I plan to commit in a day or two.

> DistanceFilter problem with deleted documents
> ---------------------------------------------
>                 Key: LUCENE-1571
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: contrib/spatial
>         Environment: N/A
>            Reporter: Phillip Rhodes
>            Assignee: Michael McCandless
>             Fix For: 2.9
>         Attachments: LUCENE-1571.patch
> I know this is the locallucene lib, but wanted to make sure we don't get this bug when
it gets into lucene contrib.
> I suspect that the issue is that deleted documents are trying to be evaluated by the
filter.  I did some debugging and I confirmed that it is bombing on a document that is marked
as deleted (using Luke).
> Thanks!
> Using the locallucene library 1.51, I get a NullPointerException at line 123 of DistanceFilter
> The method is 	public BitSet bits(IndexReader reader) 
> The line is double x = NumberUtils.SortableStr2double(sx);
> The stack trace is:
> java.lang.NullPointerException
> 	at org.apache.solr.util.NumberUtils.SortableStr2long(
> 	at org.apache.solr.util.NumberUtils.SortableStr2double(
> 	at
> 	at
> 	at
> 	at
> 	at
> 	at<init>(
> 	at

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message