[
https://issues.apache.org/jira/browse/SOLR-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13171259#comment-13171259
]
Hoss Man commented on SOLR-2976:
--------------------------------
FYI: doing some code skimming the current implications of this are:
* QEC will unneccessarily fail to work if your uniqueKey is a precisionStep=0
TrieField
* stats.facet will mistakenly refuse to facet on a multiValued=false
precisionStep=0 TrieField
Related thread:
http://www.mail-archive.com/[email protected]/msg60073.html
> 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]
