[SOLR-2976] stats.facet no longer works on single valued trie fields that don't use precision step

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Affects Version/s: 3.5
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 16/Dec/11 22:13
• Updated: 04/Jul/13 11:18

Description

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...

<fieldType name="long" class="solr.TrieLongField" precisionStep="0" omitNorms="true" />
<field name="ts" type="long" indexed="true" stored="true" required="true" multiValued="false" />

...stats.facet will not work.

Issue Links

• is broken by: SOLR-2981 multiple stats.facet params duplicate stats faceting output
• is broken by: SOLR-1023 StatsComponent should support dates (and other non-numeric fields)
• relates to: SOLR-2981 multiple stats.facet params duplicate stats faceting output