Please help test our new search server

Paul Taylor and Aurelién Mino have completed the re-write of our search server — please help us test this new code-base. Here is Paul’s write up:

This update rewrites the existing Search Indexer and Searcher with a
pure Java release whilst maintaining full compatibility with the
existing Musicbrainz Server, prototype by luks, completion by ijabz and
murdos. The aims were

1. Better performance

Search performance should be greatly improved for indexing and
especially search.

The intermediate python layer has been removed.
The webserver layer has been removed
When searching have a single Java VM , that can now be properly
The latest Lucene and Java libraries are used

2. Better Search Results

The following bugs have already been fixed

Perhaps most importantly stop words are no longer and issue so when do a
search for something that exists in the database you should always get a
match, i.e artist:”the the” or track:”is this it?”


and range queries work properly



and theres a host of other bugs and enhancements that can now be
resolved quite easily

bug list

3. Maintainability

The code has been simplified, i.e no hand coding of xml or html or
having to deal with escape characters.
Now has a full set of unit tests, can also easily generate metrics such
as code coverage reports.
No dependency on Linux or Python, making it easier for new developers
to contribute, removing the burden from ruaok.

Testing Stage

Please try it out on both as a websearch
and as an XML Service to find any omissions in functionality and any
situations where the search results aren’t good as before.

Paul / ijabz

11 thoughts on “Please help test our new search server”

  1. How old is the database ?

    Searching for X-it should give me two groups, a greenlandic one and a german one. I only get the german one on the homeip server.

  2. I don’t know if it’s related but I can’t test the AJAX search over there*.
    There is an unsolved bug #3728 I wanted to test (Search “Quốc Đại” and you don’t find him, because of the “Đ”).

    * whatever the arguments, it finds “amegnameloppy” and “rareRoyatride” only.

  3. I think the DIrect Search must be pointing to a different db to the db that the indexed search was built from so you can’t test the DIrect Search. Changes to Direct Search are not actually part of this test release.

  4. Pingback: Ludovic's weblog
  5. Hi guys,

    Since 2 days i cant find the tagger when searching on your website. i’m cataloguing my complete collection right now, but when picard doesn’t find an album, i can’t even help myself by using the website anymore. Is the feature removed or is the site buggy?

  6. @Patrique: You can add the tagger buttons back by adding a &tport=8000 to the end of the lookup URL.

  7. Worth noting that manually adding that to the URL only works on certain pages, not all. The safest way for non-experts to reopen Picard and initiate a new search (for anything) from the top search bar. Then you can do your proper searches from the website and the tagger buttons will appear until you either log out or your session expires, IIRC.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.