You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Erick Erickson (JIRA)" <ji...@apache.org> on 2014/09/08 18:00:31 UTC
[jira] [Updated] (SOLR-6386) make secondary ordering of facet.field
values (and facet.pivot?) consistently deterministic
[ https://issues.apache.org/jira/browse/SOLR-6386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Erick Erickson updated SOLR-6386:
---------------------------------
Assignee: (was: Erick Erickson)
> make secondary ordering of facet.field values (and facet.pivot?) consistently deterministic
> -------------------------------------------------------------------------------------------
>
> Key: SOLR-6386
> URL: https://issues.apache.org/jira/browse/SOLR-6386
> Project: Solr
> Issue Type: Improvement
> Reporter: Hoss Man
>
> as a fluke of how the SOLR-2894 patch evolved, it wound up adding a bit of testing of distributed facet.field on date fields (see [r1617789 changes to TestDistributedSearch|https://svn.apache.org/viewvc/lucene/dev/trunk/solr/core/src/test/org/apache/solr/TestDistributedSearch.java?r1=1617789&r2=1617788&pathrev=1617789]) ... but this started triggering some random failures due to facet constraints with identical values being sorted differently between the distributed query and the single node control query.
> We should make the facet.field (and facet.pivot) code order constraints with tied counts consistently regardless of whether it's a distrib search or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org