[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649777#action_12649777
]
Tim Sturge commented on LUCENE-1461:
------------------------------------
Paul,
Wow, I didn't realize people spent so much time on integer packing. I think
there's lots of opportunities here, particularly if this ends up in the index
(so the potential I/O cost becomes a factor as well as mem bandwidth).
I agree that TermMultiFilter is not that useful; I mostly have it because I'm
looking at TermsMultiFilter for location matching and wanted some benchmarks
versus regular filters so I could compare set implementations.
Mike,
I hadn't looked at fieldcache before, but StringIndex does seem to be the same
thing as DisjointMultiFilter (modulo using a String[] instead of a TreeMap).
I'll port RangeMultiFilter to run on top of FieldCache and check it is
identical and performs similarly (which seems like a fairly sure bet once I
figure out the FieldCache API.)
FieldCacheRangeFilter? (yeah, I know :-) )
> 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
> Attachments: DisjointMultiFilter.java, RangeMultiFilter.java,
> TermMultiFilter.java
>
>
> 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]
