Limit and order by are behaving strangely

[chaoran-chen]

I am getting strange results when using limit and orderBy together when I call the details endpoint (I haven't tested other endpoints). Sorting by country in descending order with limit 10 gives me Zimbabwe - that makes sense.

Request

curl -X 'POST' \
  'https://s1.int.genspectrum.org/open/sample/details' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "orderBy": [
    {
      "field": "country",
      "type": "descending"
    }
  ],
  "limit": 10,
  "fields": [
    "country"
  ]
}'

But if I set limit to 100, I only get Vietnam, no mention of Zimbabwe.

Request

curl -X 'POST' \
  'https://s1.int.genspectrum.org/open/sample/details' \
  -H 'accept: application/json' \
  -H 'Content-Type: application/json' \
  -d '{
  "orderBy": [
    {
      "field": "country",
      "type": "descending"
    }
  ],
  "limit": 100,
  "fields": [
    "country"
  ]
}'

I am creating this issue in LAPIS because I only directly tested LAPIS but maybe it's actually a problem in SILO?

[fengelniederhammer]

We only pass on limit and offset to SILO, so this needs to be fixed in SILO. @Taepper