krzysztof/landing_page
1
0
Fork 0
mirror of https://github.com/qdrant/landing_page.git synced 2026-09-30 16:38:31 +02:00
Code Issues Packages Projects Releases Wiki Activity

remove duplicate paragraph, oops!

Browse Source
This commit is contained in:
Luis Cossío
2024-03-01 13:48:33 -03:00
parent f57196994f
commit 05730564ef
1 changed files with 0 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
qdrant-landing/content/documentation/concepts/points.md
-2
View File
@@ -1716,8 +1716,6 @@ order_by: Some(OrderBy {
<aside role="alert">When you use the <code>order_by</code> parameter, pagination is disabled.</aside>
An ID offset does not work when the order is based on a non-unique value. Since pagination is not explicitly enabled when using `order_by`, you will not see the `next_page_offset` field in the response. However, you can use a combination of `"order_by": { "start_from": ... }` and a `{ "must_not": [{ "has_id": [...] }] }` filter to achieve the same effect.
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.
## Counting points