[
https://issues.apache.org/jira/browse/SOLR-940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677740#action_12677740
]
Uwe Schindler commented on SOLR-940:
------------------------------------
Just one question:
In queryParser you use: FieldType ft = schema.getFieldType(field); So if you
have the FieldType, why are you not able to extract the precisionStep from the
schema? The user would only have a problem, if he changes the precision step in
the schema, but with a fixed schema, that contains the precisionStep as a
parameter, you should be able to search indexed data. If you change the schema,
you have to reindex (or use a precisionStep that is a multiple of the original
one, see trie Javadoc: if you have indexed with step 2, you can search without
problems using step 4)
By the way: For future usage, you could use TrieUtils.get[Int|Long]SortField
for FieldType.getSortField instead of using SortField.String. If the problem
with more than one field name is solved, sorting works using the Trie-SortField
using the correct parser.
> 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
>
>
> 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.
