[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12724322#action_12724322
]
Uwe Schindler commented on LUCENE-1461:
---------------------------------------
Mike: There is one thing, I wanted to know, as I am not so familar with the
whole internal query handling:
The DocIdSet for the native numeric types may return document ids, that are
deleted (because for native types there is no possibility to find out if there
was no term saved, null-fields or deleted docs would simply have 0 in the field
cache array). A range covering 0 always returns all doc ids of deleted docs or
docs without a numeric field (this can be noted in the javadocs: "for numeric
queries every document must have exact *one* numeric term per field"). Is this
a problem, will the false-hits in the iterator be filted because doc is deleted?
In the case of an real filter the query, that is filtered will not return
deleted docs, but a ConstantScoreQuery on this filter would return deleted docs?
> Cached filter for a single term field
> -------------------------------------
>
> Key: LUCENE-1461
> URL: https://issues.apache.org/jira/browse/LUCENE-1461
> Project: Lucene - Java
> Issue Type: New Feature
> Reporter: Tim Sturge
> Assignee: Uwe Schindler
> Fix For: 2.9
>
> Attachments: DisjointMultiFilter.java, FieldCacheRangeFilter.patch,
> LUCENE-1461.patch, LUCENE-1461.patch, LUCENE-1461.patch, LUCENE-1461.patch,
> LUCENE-1461a.patch, LUCENE-1461b.patch, LUCENE-1461c.patch,
> RangeMultiFilter.java, RangeMultiFilter.java, TermMultiFilter.java,
> TestFieldCacheRangeFilter.patch
>
>
> These classes implement inexpensive range filtering over a field containing a
> single term. They do this by building an integer array of term numbers
> (storing the term->number mapping in a TreeMap) and then implementing a fast
> integer comparison based DocSetIdIterator.
> This code is currently being used to do age range filtering, but could also
> be used to do other date filtering or in any application where there need to
> be multiple filters based on the same single term field. I have an untested
> implementation of single term filtering and have considered but not yet
> implemented term set filtering (useful for location based searches) as well.
> The code here is fairly rough; it works but lacks javadocs and toString() and
> hashCode() methods etc. I'm posting it here to discover if there is other
> interest in this feature; I don't mind fixing it up but would hate to go to
> the effort if it's not going to make it into Lucene.
--
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: [email protected]
For additional commands, e-mail: [email protected]
