[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated SOLR-940:
-------------------------------
Attachment: SOLR-940-LUCENE-1701-addition.patch
Hi Shalin,
here is an additional patch (but only for the trie parts), that is more
intelligent and also uses NumericTokenStream for the query time factory. Your
previous patch must be applied, then revert the changes in
analysis.TrieXxxxTokenizerFactory and TrieField. Then apply the patch, which
removes the old factories and creates a new one TrieTokenizerFactory. It should
compile, but not really tested (it is hard to apply all your changes). If there
are compile errors, they can be easily fixed :-)
The idea is to use the same tokenstream for query time analysis. To only
produce the highest precision token needed for that, it is simply using a
precisionStep of 32 for int/float and 64 for long/double/date of the former
TrieIndexTokenizerFactory. No magic with KeywordTokenizer needed. NumericUtils,
which is a expert Lucene class (not really public) is not needed anymore.
> TrieRange support
> -----------------
>
> Key: SOLR-940
> URL: https://issues.apache.org/jira/browse/SOLR-940
> Project: Solr
> Issue Type: New Feature
> Reporter: Yonik Seeley
> Assignee: Shalin Shekhar Mangar
> Fix For: 1.4
>
> Attachments: SOLR-940-LUCENE-1602.patch, SOLR-940-LUCENE-1602.patch,
> SOLR-940-LUCENE-1701-addition.patch, SOLR-940-LUCENE-1701.patch,
> SOLR-940-LUCENE-1701.patch, SOLR-940-newTrieAPI.patch,
> SOLR-940-newTrieAPI.patch, SOLR-940-rangequery.patch,
> SOLR-940-rangequery.patch, SOLR-940-test.patch, SOLR-940.patch,
> SOLR-940.patch, SOLR-940.patch, SOLR-940.patch, SOLR-940.patch,
> SOLR-940.patch, SOLR-940.patch, SOLR-940.patch, 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.
