[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676723#action_12676723
]
Shalin Shekhar Mangar commented on SOLR-940:
--------------------------------------------
bq. Now I understand the problem, Yonik had with the original TrieRange
implementation and wanted to change the API. Your problem is, that you must be
able to not just map the numerical value to one field and token. You have to
index one numeric value to more than one token before indexing them.
I was just reading Yonik's comment on java-dev to figure out what Yonik had in
mind. Normally, the toInternal/toExternal methods take care of
encoding/decoding. But we cannot use them because the trie encoding produces
multiple tokens. That can be done through a tokenizer as you said. But, a
tokenizer cannot add tokens in another field which is requred for the filter to
work correctly.
> 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
>
>
> 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.
