The media scanner does not sort the results of search queries

[James Henstridge]

To perform searches, the media scanner uses a custom Collector class that implements the offset/limit behaviour and passes the results off to an ItemVistor (sic) callback function.

However, results are passed to a Lucene collector either in document ID order or an undefined order (depending on what the collector returns from its acceptsDocsOutOfOrder()) method. This means that for broad searches, the most relevant results probably won't be at the top, and may even get cut off if a result limit has been specified.

[PS Jenkins bot (ps-jenkins)]

Fix committed into lp:mediascanner at revision 389, scheduled for release in mediascanner, milestone Unknown

[Launchpad Janitor (janitor)]

This bug was fixed in the package mediascanner - 0.3.93+13.10.20131011-0ubuntu1

---------------
mediascanner (0.3.93+13.10.20131011-0ubuntu1) saucy; urgency=low

  [ Michal Hruby ]
  * Increase discovery timeout, log why discovery failed. (LP: #1236878,
    #1234726)

  [ James Henstridge ]
  * If a limit on the number of results for a search is given, sort the
    results. (LP: #1234145)
  * Download album art to the media art cache during scanning rather
    than storing remote URLs in the index.
  * Depend on ca-certificates to fix test failure caused by libsoup
    warnings about missing /etc/ssl/certs/ca-certificates.crt.

  [ Jussi Pakkanen ]
  * Download album art to the media art cache during scanning rather
    than storing remote URLs in the index.

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 392
 -- Ubuntu daily release <email address hidden> Fri, 11 Oct 2013 09:20:33 +0000