[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677801#action_12677801
]
Uwe Schindler commented on SOLR-940:
------------------------------------
About the sorting problem:
As already discussed in the original TrieRange issue, the sorting is a problem
for trie encoded fields. The problem is, that the current FieldCache has two
problems:
- it stores the *last* term (the last term in the TermEnum!) in the cache
- it throws an exception, when the number of term in one field > the number of
docs (I think this was the case)
For trie fields it would be good, to have something like "sorting on the first
term of the document". This would be conformant with TrieRange, as the first
term in trieCodeXxx() is always the highest precision one (and also in your
tokenizer). I think, we should discuss more in LUCENE-1372, where this sorting
problem is discussed. If it would be fixed before 2.9, I could remove the whole
multi-field parts out of TrieRange API and only support one field name (with
what I would be really happy). Then you can index all trie terms in one field
and sort on it (if the order of generated trie terms is preserved through the
whole indexing and TermDocs array (which is not really simple for the field
cache to handle).
> TrieRange support
> -----------------
>
> Key: SOLR-940
> URL: https://issues.apache.org/jira/browse/SOLR-940
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Fix For: 1.4
>
> Attachments: SOLR-940.patch, SOLR-940.patch
>
>
> We need support in Solr for the new TrieRange Lucene functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
