On Tue, 20 Sept 2022 at 17:41, Robert Newson <[email protected]> wrote: > > The bookmark encodes the "order" property of the last result from each shard > range, and a query with a bookmark parameter is simply retrieving matches > that come after those order values. If the database changes between queries > (documents added, changed or removed) such that the overall ordering of > search results also changes, it is normal to see search results repeated (a > database change added an item to a previous page, pushing every later change > further down the list) or missing (a database change removed an item from a > previous page, moving everyone "up").
I do not think this applies to my case: I executed a query for documents in a given "created_at" date range, hence the results are not influenced by the additions of further documents (which by necessity have a "created_at" date outside that range}. Cheers, Luca Morandini
