From 3901c4a698db57c7842a098997d42738be4612fa Mon Sep 17 00:00:00 2001 From: timvisee Date: Fri, 5 Jul 2024 12:03:16 +0200 Subject: [PATCH] Remove note about getting duplicate points if matching multiple payloads --- qdrant-landing/content/documentation/concepts/points.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/qdrant-landing/content/documentation/concepts/points.md b/qdrant-landing/content/documentation/concepts/points.md index f86fcee3d..97f308d0f 100755 --- a/qdrant-landing/content/documentation/concepts/points.md +++ b/qdrant-landing/content/documentation/concepts/points.md @@ -1751,8 +1751,6 @@ new OrderBy }; ``` -**Note:** for payloads with more than one value (such as arrays), the same point may show up more than once. Each point can appear as many times as the number of elements in the array. For example, if you have a point payload with a `timestamp` key, and the value for the key is an array of 3 elements, the same point will appear 3 times in the results, one for each timestamp. - When sorting is based on a non-unique value, it is not possible to rely on an ID offset. Thus, next_page_offset is not returned within the response. However, you can still do pagination by combining `"order_by": { "start_from": ... }` with a `{ "must_not": [{ "has_id": [...] }] }` filter.