[
https://issues.apache.org/jira/browse/LUCENE-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12650994#action_12650994
]
Michael McCandless commented on LUCENE-1461:
--------------------------------------------
bq. But you still store strings in the index. So essentially you'll convert
your value from T to String, store it, retrieve it, convert back to T in such a
custom comparator, and finally compare. Why should I need that second
conversion and custom comparators, if I can have order-preserving bijective
T<->String relation?
True, since you'll need to xform anyway for non-textual fields. Or maybe
eventually we can simply allow T to be the key in the terms dict (so long as
T.compareTo(T) exists), which KS/Lucy apparently does.
> 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: Michael McCandless
> Attachments: DisjointMultiFilter.java, LUCENE-1461.patch,
> LUCENE-1461a.patch, LUCENE-1461b.patch, RangeMultiFilter.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]
