While the new feature basically works, we have a different search result in Solr for an empty value. The test expects:

'[EMPTY]',
'article_category',
'article_category',
'dutch category 1',
'dutch category 2',
'dutch category 3',
'dutch category 4',
'dutch category 5',
'item_category',
'item_category',

Solr returns:

'article_category',
'article_category',
'dutch category 1',
'dutch category 2',
'dutch category 3',
'dutch category 4',
'dutch category 5',
'item_category',
'item_category',
'[EMPTY]',

So the the only difference is '[EMPTY]'. All other values are sorted correctly.

CommentFileSizeAuthor
#3 2825086.patch8.14 KBmkalkbrenner

Comments

mkalkbrenner created an issue. See original summary.

mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Title: Tests for click sorts in views fail on Solr » Results for sorting by missing fields differs from DB backend
Priority: Normal » Major
mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
StatusFileSize
new 2825086.patch8.14 KB

This patch makes sorting on Solr behave like the DB backend. Since this is the default behavior of Lucene anyway, we should do it.

  • mkalkbrenner committed d3b11df on 8.x-1.x 
    Issue #2825086 by mkalkbrenner: Results for sorting by missing fields...
mkalkbrenner’s picture

mkalkbrenner
Primary language German
Location 🇩🇪
commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.