[ 
https://issues.apache.org/jira/browse/SOLR-14477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Chris M. Hostetter updated SOLR-14477:
--------------------------------------
    Attachment: SOLR-14477.patch
        Status: Open  (was: Open)


I've updated the patch to include a new {{TestCloudJSONFacetSKGEquiv}} based on 
the work we've been doing over in SOLR-13132 (this is essentially 
{{TestCloudJSONFacetSKGSweep}} but with the {{sweep_collection}} permutations 
ripped out)

Seeds like this pass with the current patch, but fail w/fix to 
FacetFieldProcessorByArray reverted...

{noformat}
ant test  -Dtestcase=TestCloudJSONFacetSKGEquiv 
-Dtests.method=testBespokePrefix -Dtests.seed=CC51A971B35AB0A3 
-Dtests.slow=true -Dtests.badapples=true -Dtests.locale=gsw-FR 
-Dtests.timezone=Mexico/BajaSur -Dtests.asserts=true -Dtests.file.encoding=UTF-8
{noformat}

----

Unfortunately -- it's Turtles all the way down...

This more robust randomizd testing to have uncovered a new (unrelated to SKG) 
in dvhash: SOLR-14492.

i need to fix that, so that we can beast this new test and prove it's ready to 
commit (or find more existing blocker bugs/turtles)



> relatedness() values can be wrong when using 'prefix'
> -----------------------------------------------------
>
>                 Key: SOLR-14477
>                 URL: https://issues.apache.org/jira/browse/SOLR-14477
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Chris M. Hostetter
>            Assignee: Chris M. Hostetter
>            Priority: Major
>         Attachments: SOLR-14477.patch, SOLR-14477.patch, SOLR-14477.patch
>
>
> Another {{relatedness()}} bug found in json facet's while working on 
> increased test coverage for SOLR-13132.
> if the {{prefix}} option is used when doing a terms facet, then the 
> {{relatedess()}} calculations can be wrong in some situations -- most notably 
> when using {{limit:-1}} but i'm pretty sure the bug also impacts the code 
> paths where the (first) {{sort}} (or {{prelim_sort}} is computed against the  
> {{relatedness()}} values.
> Real world impacts of this bug should be relatively low since i can't really 
> think of any practical usecases for using  {{relatedness()}} in conjunction 
> with {{prefix}}



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

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

Reply via email to