Uploaded image for project: 'MusicBrainz Server'
  1. MusicBrainz Server
  2. MBS-12154

MB Search API is broken, no pagination possible

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Search, Web service
    • None

      MB Search API documentation says you can use offset and limit to paginate the results of a query, but it does not work:

      /ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>

      Try with a query that returns more than 100 results, try with offset=0 or offset=101.
      Results are ordered randomly.
      If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.

      So the offset system is broken, since SOLR, probably?

      Could we have a sort order set for all queries? It could be anything like, for instance, order by row ID.

      Old description, before noticing it was a global issue:

      I try to use /ws/2/work?query=…&offset=x&limit=y in JSON.
      The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

      Therefore it's impossible to use this web service when there can be more than 100 results.

          [MBS-12154] MB Search API is broken, no pagination possible

          Nicolás Tamargo made changes -
          Assignee New: Alastair Porter [ alastairp ]
          GitHub Bot made changes -
          Status Original: Open [ 1 ] New: Review Submitted [ 5 ]
          jesus2099 made changes -
          Link New: This issue is related to MBS-5636 [ MBS-5636 ]
          jesus2099 made changes -
          Description Original: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use *offset* and *limit* to paginate the results of a *query*, but it does not work:

          {{/ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          		New: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use *offset* and *limit* to paginate the results of a *query*, but it does not work:

          {{/ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          *Could we have a sort order set for all queries?* It could be *anything* like, for instance, *order by row ID*.

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          jesus2099 made changes -
          Description Original: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{/ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          		New: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use *offset* and *limit* to paginate the results of a *query*, but it does not work:

          {{/ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          jesus2099 made changes -
          Description Original: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{/ws/2/<entity>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          		New: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{/ws/2/<entity-type>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          jesus2099 made changes -
          Description Original: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{https://musicbrainz.org/ws/2/&lt;entity&gt;/?query=&lt;query&gt;&limit=100&offset=&lt;offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          		New: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{/ws/2/<entity>/?query=<query>&limit=100&offset=<offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          jesus2099 made changes -
          Component/s New: Search [ 10003 ]
          jesus2099 made changes -
          Description Original: I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          		New: [MB Search API documentation|https://wiki.musicbrainz.org/MusicBrainz_API/Search] says you can use offset and limit to paginate the results:

          {{https://musicbrainz.org/ws/2/&lt;entity&gt;/?query=&lt;query&gt;&limit=100&offset=&lt;offset>}}

          Try with a query that returns more than 100 results, try with {{offset=0}} or {{offset=101}}.
          Results are ordered randomly.
          *If you paginate through all possible offsets to collect all results, you will have duplicates of some items and you will miss other items, randomly, always.*

          So the *offset* system is broken, since SOLR, probably?

          ----

          Old description, before noticing it was a global issue:

          I try to use /ws/2/*work*?query=…&offset=x&limit=y in JSON.
          The results are never ordered in the same fashion, even between two calls of the same query and same limit with a different offset to fetch pages.

          Therefore it's impossible to use this web service [when there can be more than 100 results|https://github.com/jesus2099/konami-command/issues/174#issuecomment-1008267401].
          jesus2099 made changes -
          Summary Original: Cannot paginate /ws/2/work?query= with offset as work search web service results are not ordered New: MB Search API is broken, no pagination possible

            alastairp Alastair Porter
            jesus2099 jesus2099
            Votes:
            3 Vote for this issue
            Watchers:
            9 Start watching this issue

              Created:
              Updated:

                Version Package