[
https://issues.apache.org/jira/browse/LUCENE-1541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12675390#action_12675390
]
Ning Li commented on LUCENE-1541:
---------------------------------
When one precision step is given, it is converted to the representation. Then
no array creation is necessary. But something like TrieUtils.FieldConfiguration
would be better. Besides the field name and the precision steps, either it
should also contain a type (long/int) or a subclass is created for each type.
It can be used both at indexing time and at query time.
> Trie range - make trie range indexing more flexible
> ---------------------------------------------------
>
> Key: LUCENE-1541
> URL: https://issues.apache.org/jira/browse/LUCENE-1541
> 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: java-dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: java-dev-h...@lucene.apache.org
