lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From " (JIRA)" <>
Subject [jira] [Commented] (SOLR-2976) stats.facet no longer works on single valued trie fields that don't use precision step
Date Wed, 19 Dec 2012 22:43:17 GMT

] commented on SOLR-2976:

Hit this problem recently.
To fix this problem. and support facet search on this field, I have to create another field,
 with precisionStep="2147483647"(Integer,MAX_VALUE), this is not good, as it takes more disk
size, and it's hard to explain to customers why we need this field.

So do we have plan to fix this problem? Thanks :)
> stats.facet no longer works on single valued trie fields that don't use precision step
> --------------------------------------------------------------------------------------
>                 Key: SOLR-2976
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 3.5
>            Reporter: Hoss Man
>            Assignee: Ryan McKinley
>         Attachments: SOLR-2976_3.4_test.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
> 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:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message