[
https://issues.apache.org/jira/browse/SOLR-2976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Muir updated SOLR-2976:
------------------------------
Attachment: SOLR-2976.patch
As adrien mentioned, the underlying issue is fixed (stats.facet implemented
differently).
However, its still bogus that this fieldtype returns true for isTokenized(),
and that it has a crazy custom attribute-wrapping TrieTokenizerFactory that is
totally unnecessary: at index-time createField() is just using
IntField/FloatField/etc, for range-queries the analyzer is also not used (it
forms getRangeQuery), and for term-queries getFieldQuery already does the right
thing.
This patch removes this stuff.
> stats.facet no longer works on single valued trie fields that don't use
> precision step
> --------------------------------------------------------------------------------------
>
> Key: SOLR-2976
> URL: https://issues.apache.org/jira/browse/SOLR-2976
> Project: Solr
> Issue Type: Bug
> Affects Versions: 3.5
> Reporter: Hoss Man
> Attachments: SOLR-2976_3.4_test.patch, SOLR-2976.patch,
> SOLR-2976.patch
>
>
> As reported on the mailing list, 3.5 introduced a regression that prevents
> single valued Trie fields that don't use precision steps (to add course
> grained terms) from being used in stats.facet.
> two immediately obvious problems...
> 1) in 3.5 the stats component is checking if isTokenzed() is true for the
> field type (which is probably wise) but regardless of the precisionStep used,
> TrieField.isTokenized is hardcoded to return true
> 2) the 3.5 stats faceting will fail if the FieldType is multivalued - it
> doesn't check if the SchemaField is configured to be single valued
> (overriding the FieldType)
> 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}
> ...stats.facet will not work.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
