[jira] [Commented] (SOLR-5443) SolrQuery addDateRangeFacet & addNumericRangeFacet should use local params instead of field prefix params

["Hoss Man (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SOLR-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823074#comment-13823074 ] 

Hoss Man commented on SOLR-5443:
--------------------------------

Note: workarround is to just call {code}SolrQuery.add("facet.range","{!facet.range.start=... facet.range.end=... ...}fieldName"){code} instead of using either of these sugar methods.

> SolrQuery addDateRangeFacet & addNumericRangeFacet should use local params instead of field prefix params
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: SOLR-5443
>                 URL: https://issues.apache.org/jira/browse/SOLR-5443
>             Project: Solr
>          Issue Type: Improvement
>            Reporter: Hoss Man
>
> The syntactic sugar methods  addDateRangeFacet & addNumericRangeFacet currently generate multiple "f.fieldName.facet.range..." params from their input, but this causes problems when users try to facet on the same fields in multiple ways -- these methods should instead generate a single facet.field param for the specified field name, using nested local params for hte start/end/gap options. (see SOLR-1351)



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org