[
https://issues.apache.org/jira/browse/SOLR-4842?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Erik Hatcher updated SOLR-4842:
-------------------------------
Attachment: SOLR-4842.patch
Here's a patch that demonstrates the issue clearly. The actual problem
reported to me (via a customer) was about facet.prefix, but I tried to distill
it to the mincount initially missing the weird mincount/zeros interaction.
I've added two test cases, one that passes as-is, the second fails, and the
only difference is the order of the two facet.field params, one using a
localparam of facet.prefix, the other not.
> Field faceting with local params affects successive field faceting parameters
> -----------------------------------------------------------------------------
>
> Key: SOLR-4842
> URL: https://issues.apache.org/jira/browse/SOLR-4842
> Project: Solr
> Issue Type: Bug
> Components: search, SearchComponents - other
> Affects Versions: 4.3
> Reporter: Erik Hatcher
> Assignee: Erik Hatcher
> Priority: Critical
> Attachments: SOLR-4842__hoss_tests.patch, SOLR-4842.patch,
> SOLR-4842.patch
>
>
> SOLR-4717 introduced local param support for per-field faceting, allowing the
> same field to be faceted in various ways. There's a problem such that one
> fields local param setting will override the defaults of the next field. For
> example: {code}facet.field={!key=foo facet.mincount=1
> facet.missing=false}field&facet.field={!key=bar
> facet.missing=true}field{code} causes the "bar" faceting to use
> facet.mincount=1 when it should use the default of 0.
--
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]
