Uploaded image for project: 'Solr'
  1. Solr
  2. SOLR-15048

collapse + query elevation behaves inconsistenty w/ 'null group' docs depending on group head selector

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 8.8, main (9.0)
    • Component/s: None
    • Labels:
      None

      Description

      while working on SOLR-15047, I realized I wasn't really clear on what the expected semantics of were suppose to be when "boosting"
       docs that had null values in the collapse field.

      I expanded on my test from that jira, to demonstrate the logic i (thought) i understood from the Ord based collector - but then discovered that depending on the group head selector used (ie: OrdScoreCollector vs OrdFieldValueCollector+OrdIntStrategy vs OrdFieldValueCollector+OrdValueSourceStrategy , etc...) you get different behavior - not just in what group head is selected, but even when the behavior should be functionally equivilent, you can get different sets of groups. (even for simple string field collapsing, independent of the bugs in numeric field collapsing).

       

      I have not dug into WTF is happening here, but I'll attach my WIP test

        Attachments

        1. SOLR-15048.patch
          8 kB
          Chris M. Hostetter
        2. SOLR-15048.patch
          15 kB
          Chris M. Hostetter
        3. SOLR-15048.patch
          21 kB
          Chris M. Hostetter
        4. SOLR-15048.patch
          53 kB
          Chris M. Hostetter

        Issue Links

          Activity

            People

            • Assignee:
              hossman Chris M. Hostetter
              Reporter:
              hossman Chris M. Hostetter

              Dates

              • Created:
                Updated:
                Resolved:

                Issue deployment