[
https://issues.apache.org/jira/browse/SOLR-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171274#comment-13171274
]
Uwe Schindler commented on SOLR-2976:
-------------------------------------
Hi Hoss,
in general the precisionStep is somehow inconsistent between Solr and Lucene.
The problem is that precisionStep==0 is not defined at all. The minimium
precision step in Lucene is 1 and means lot's of terms per distinct value. What
Solr defines as precisionStep 0 is in Lucene everything >= 64 (for longs) or >=
32 for ints.
In general it is confusing that we have two precSteps. I would prefer it in
this issue to clean this up and make the solr schema simply allow a symbolic
constant for the precision step (as 0 makes no sense and infinite is not a
valid number in Integer.valueOf). How about precisionStep="infinite", because
that would be consistent with Lucene. For backwards compatibility, 0 could
still be supported, but Lucene throws IAE.
> TrieField.isTokenized returns true regardless of precisionStep
> --------------------------------------------------------------
>
> Key: SOLR-2976
> URL: https://issues.apache.org/jira/browse/SOLR-2976
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.5
> Reporter: Hoss Man
>
> regardless of the precisionStep used, TrieField.isTokenized is hardcoded to
> return true -- so even if a user has something like this in their schema...
> {code}
> <fieldType name="long" class="solr.TrieLongField" precisionStep="0"
> omitNorms="true" />
> <field name="ts" type="long" indexed="true" stored="true" required="true"
> multiValued="false" />
> {code}
> ...any code paths that are driven by isTokenized will think their may be
> multiple terms per document when in reality there is at most one.
> we should consider redefining TrieField.isTokenized to be something like...
> {code}
> @Override
> public boolean isTokenized() {
> return Integer.MAX_VALUE != precisionStep;
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
