Add definitions of the missing behaviors for the sort specification

[gmourier]

• In the case where an attribute is specified as a sort criterion at search time and if this attribute is of a different type between several documents, the numeric type will always be favored first by the engine. This means that documents with numeric values for this attribute will be sorted before those with string values. This can lead to awkward sorting behavior, so the user should make sure to have the same type on the attribute he wants to sort on for all these documents.

• In the case where an attribute is specified as a sort criterion at search time and does not exist on a document, the document will be placed at the end of the ranking rule sort.

[github-actions]

🤖 API change detected:

Updated: GET /indexes/{indexUid}/search
  Query parameter added: sort
Updated: POST /indexes/{indexUid}/search
  Body attribute added: sort
Updated: GET /indexes/{indexUid}/updates
  Response modified: 200
Updated: GET /indexes/{indexUid}/updates/{updateId}
  Response modified: 200
Updated: GET /indexes/{indexUid}/settings
  Response modified: 200
    Body attribute added: sortableAttributes
Updated: POST /indexes/{indexUid}/settings
  Body attribute added: sortableAttributes
Added: GET /indexes/{indexUid}/settings/sortable-attributes
Added: POST /indexes/{indexUid}/settings/sortable-attributes
Added: DELETE /indexes/{indexUid}/settings/sortable-attributes

View documentation diff

Powered by Bump

[Kerollmops]

Nothing to say, that's good to me! You can see the advancement of this feature on milli.