[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-1461:
----------------------------------
Attachment: LUCENE-1461.patch
Patch that implements all FieldCache data types. The Double/Float includesXxxx
code is a littly bit a hack, I will think about it again.
What is currently not consistent for all types of range queries (RangeQuery,
NumericRangeQuery, FieldCacheRangeFilter) is, if it is allowed to have one
bound null and include it. In my opinion, this should always be allowed and
should deliver same results for inclusive or not.
There is a first test together with TrieRangeQuery (for ints) in
TestNumericRangeQuery32.java - which passes.
An important restricion for this type with numeric field caches is: There must
be exactly one value per document. If value is missing, 0 is assumed. For
Strings, no value is allowed, not for numbers (because arrays like int[] cannot
contain null values).
> 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-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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
