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

John Gibson edited comment on SOLR-6193 at 6/23/14 6:23 PM:
------------------------------------------------------------

Here's a patch for an existing unit test on the lucene_solr_4_8 branch that 
illustrates the issue.

Also note that while working on this I noticed that the facet.limit local 
parameter is ignored for both the regular and distributed versions of the 
search. Is that intentional? Or a bug?


was (Author: jgibson):
Here's a patch for an existing unit test that illustrates the issue.

Also note that while working on this I noticed that the facet.limit local 
parameter is ignored for both the regular and distributed versions of the 
search. Is that intentional? Or a bug?

> Distributed search with multiselect faceting ignores the facet.offset local 
> parameter
> -------------------------------------------------------------------------------------
>
>                 Key: SOLR-6193
>                 URL: https://issues.apache.org/jira/browse/SOLR-6193
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.8.1
>         Environment: OS X 10.9.3 Apache Tomcat 7.0.41
> Debian Apache Tomcat 7
>            Reporter: John Gibson
>         Attachments: bad_facet_offset_test_4_8_x.patch
>
>
> When a distributed search contains multiselect faceting the per-field 
> faceting options are not honored for alternate selections of the field. For 
> example with a query like:
> {noformat}
> facet.field=blah&facet.field={!key myblah 
> facet.offset=10}blah&f.blah.facet.offset=20
> {noformat}
> The returned facet results for both blah and myblah will use an offset of 20 
> as opposed to a standard search returning myblah with an offset of 10.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to