Hello, We have a query with LIMIT 100. There is no ORDER BY. The query with WHERE clause with value-A returns 2 docs and takes ~25 seconds whereas with value-B it returns 100 docs but takes only 300 millisec. For value-B, there are ~99k docs in the database whereas for value-A there are only 2 doc…

As there is no ORDER BY, you want any 100 documents. If all the predicates are pushed to indexer and no false positives possible the limit will be pushed to index scan and indexer only produces limit documents. This best case scenario. Other wise query works as normal produces results. When final …

LIMIT clause and Indexscan

Couchbase Server

system Closed September 11, 2023, 1:32pm 8

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Index Service Returns All Documents and then it Sorts SQL++	10	683	September 22, 2020
Missing results when using WHERE, LIMIT and OFFSET without an ORDER BY SQL++	2	956	February 8, 2021
Couchbase 4.1.1 CE - slow query when no limit is specified SQL++ n1ql	7	1471	December 16, 2016
Understanding Query plan stats Couchbase Server query	13	2657	December 6, 2019
Index Scan timesout on limiting condition SQL++ n1ql , index	11	2887	January 1, 2020

LIMIT clause and Indexscan

Related topics