Incorrect behaviour of search service

Steps to reproduce

From the Search Service REST docs:
id: The ID of the single episode to be returned, if it exists.

% curl -s 'http://localhost:8080/search/episode.xml?id=355e63c5-8637-4819-874b-47effa3e9386' | xmllint --format - | grep -B1 '<ns2:title>'
<ns2:mediapackage start="2013-07-17T12:58:00Z" id="4070e20f-424e-4635-bbea-6ee1cf1782a1" duration="3422">

<ns2:mediapackage start="2013-07-17T12:57:00Z" id="7070f50b-e3d6-4dcd-8846-0d94ad33f372" duration="3480">

It's obvious neither a single episode nor does any of the episode ids match. The behaviou of “id” is more like the one of “sid” for which the docs say:
sid: Any episode that belongs to specified series id.


Tobias Wunden
October 8, 2013, 2:22 PM

I suggest splitting this into a new ticket, so the fixes for the first problem can be merged to 1.4.1.

Lukas Rohner
October 8, 2013, 2:26 PM

It's already merged to 1.4.1

Greg Logan
October 8, 2013, 3:48 PM

Per the discussion in the devops meeting today, this is done and any further work will be split off into another ticket.

Lars Kiesow
October 8, 2013, 3:57 PM

As discussed in the DevOps meeting. I created two new issues for the remaining bugs:
– /search/series.xml – series switch disables all results
– /search/series.xml – Search for series identifier may return episodes

Will now close this one.

Lars Kiesow
October 8, 2013, 3:58 PM

…Greg was faster

Fixed and reviewed


Lukas Rohner


Lars Kiesow


Incorrectly Functioning Without Workaround

Tags (folksonomy)


Fix versions

Affects versions