lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Uwe Schindler (JIRA)" <>
Subject [jira] Commented: (LUCENE-1541) Trie range - make trie range indexing more flexible
Date Fri, 20 Feb 2009 07:27:04 GMT


Uwe Schindler commented on LUCENE-1541:

That would be a possibility, but not understandable for users :-). My problem was, that for
each invocation of the simple trieCodeLong/Int() methods (taking only one precision step),
the array is created in the inner expert method call. Maybe I revert to use the old code for
this specific case here. When indexing documents, you need to call this method very often.

But Java5 uses the same technique for varargs and also allocates the array on each call, so
I do not think this is a real problem.

Maybe another solution for all this (and would make API simplier and more extensible without
changing method parameters) would be to use a helper class TrieUtils.FieldConfiguration that
contains the precision steps and field names (and maybe more in future). A user could instantiate
one of this helpers for each field and reuse it, passing it to the relevant methods (accepting
field names and precision steps). These methods/ctors would then only exist once (not overloaded).

I wanted also talk with Yonik about it, what he thinks.

> Trie range - make trie range indexing more flexible
> ---------------------------------------------------
>                 Key: LUCENE-1541
>                 URL:
>             Project: Lucene - Java
>          Issue Type: Improvement
>          Components: contrib/*
>    Affects Versions: 2.9
>            Reporter: Ning Li
>            Assignee: Uwe Schindler
>            Priority: Minor
>             Fix For: 2.9
>         Attachments: LUCENE-1541.patch
> In the current trie range implementation, a single precision step is specified. With
a large precision step (say 8), a value is indexed in fewer terms (8) but the number of terms
for a range can be large. With a small precision step (say 2), the number of terms for a range
is smaller but a value is indexed in more terms (32).
> We want to add an option that different precision steps can be set for different precisions.
An expert can use this option to keep the number of terms for a range small and at the same
time index a value in a small number of terms. See the discussion in LUCENE-1470 that results
in this issue.

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:
For additional commands, e-mail:

View raw message