Mailing-List: contact java-dev-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: java-dev@lucene.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
From: "Uwe Schindler" <uwe@thetaphi.de>
To: <java-dev@lucene.apache.org>
References: <BD2A44BA-7FD6-4024-94A3-CE6C2F3A86A0@mikemccandless.com>
 <839A8626-1D06-4D99-9111-607179E029DD@osafoundation.org>
 <59b3eb370903181331w16198ae3rd4bff6b57342cc79@mail.gmail.com>
Subject: RE: move TrieRange* to core?
Date: Wed, 18 Mar 2009 22:45:06 +0100
Message-ID: <246F22F7AC094C3A85315CD564319005@VEGA>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="utf-8"
Content-Transfer-Encoding: quoted-printable
In-Reply-To: <59b3eb370903181331w16198ae3rd4bff6b57342cc79@mail.gmail.com>
Thread-Index: AcmoCJFvUWExEVYYSmmFtZhTmTJ2+gACCtdg

> >> I think we should move TrieRange* into core before 2.9?
> >>
> >> It's received alot of attention, from both developers (Uwe & Yonik =
did
> >> lots of iterations, and Solr is folding it in) and user interest.
> >>
> >> It's a simpler & more scalable way to index numeric fields that you
> >> intend to sort and/or do range querying on; we can do away with =
tricky
> >> number padding.
> >>
> >> Plus it's just plain cool :)
> >>
> >> I also think we should change its name.  I know and love "trie", =
but
> >> it's a very technical term that's not immediately meaningful to =
users
> >> of Lucene's API.  Plus I've learned from doing too many renamings
> >> lately that it's best to try to get the name right at the start.
> >>
> >> Maybe just NumberUtils, IntRangeFilter, LongRangeFilter,
> >> AbstractNumberRangeFilter?
> >
> > +1
> >
> > How about NumericRangeFilter ?
> The idea behind this filter can be applied to more than just numbers,
> so I'd like to put the stress on its speed or idea used -
> FastRangeQuery, TrieRangeQuery, SegmentedRangeQuery (from the fact it
> splits input range into variable-precision segments), PrefixRangeQuery
> (you can reword the algorithm in terms of prefixes)

Trie  is also known as Prefix Tree, because of that and the usage, I =
called it TrieRange [see http://en.wikipedia.org/wiki/Trie: the original =
term "trie" comes from "retrieval." Following the etymology, the =
inventor, Edward Fredkin, pronounces it [t=C9=B9i] ("tree"). However, it =
is pronounced [t=C9=B9a=C9=AA] ("try") by other authors].

So we have two possibilities:

- a generic name completely hiding the internals -- but then the =
complexity with the helper field should be hidden, how should =
"precisionStep" called and justified then?
- a name describing how it works, like Earwin suggested - so we could =
stay with TrieRange.=20

The name "TrieRangeQuery" first appeared in [1], so it should be noted =
somewhere, even if it is renamed to NumberRangeFilter or something =
else... :-) I would be happy with a renaming to "NumberRangeFilter", but =
"trie" should appear somewhere in the docs.

Uwe

[1] Schindler, U, Diepenbroek, M, 2008. Generic XML-based Framework for =
Metadata Portals. Computers & Geosciences 34 (12), 1947-1955. =
doi:10.1016/j.cageo.2008.02.023


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: java-dev-help@lucene.apache.org