You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Chris M. Hostetter (Jira)" <ji...@apache.org> on 2020/05/08 00:37:00 UTC

[jira] [Created] (SOLR-14467) inconsistent server errors combining relatedness() with allBuckets:true

Chris M. Hostetter created SOLR-14467:
-----------------------------------------

             Summary: inconsistent server errors combining relatedness() with allBuckets:true
                 Key: SOLR-14467
                 URL: https://issues.apache.org/jira/browse/SOLR-14467
             Project: Solr
          Issue Type: Bug
      Security Level: Public (Default Security Level. Issues are Public)
          Components: Facet Module
            Reporter: Chris M. Hostetter


While working on randomized testing for SOLR-13132 i discovered a variety of different ways that JSON Faceting's "allBuckets" option can fail when combined with the "relatedness()" function.

I haven't found a trivial way to manual reproduce this, but i have been able to trigger the failures with a trivial patch to {{TestCloudJSONFacetSKG}} which i will attach.

Based on the nature of the failures it looks like it may have something to do with multiple segments of different sizes, and or resizing the SlotAccs ?

The relatedness() function doesn't have much (any?) existing tests in place that leverage "allBuckets" so this is probably a bug that has always existed -- it's possible it may be excessively cumbersome to fix and we might nee/wnat to just document that incompatibility and add some code to try and detect if the user combines these options and if so fail with a 400 error?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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