N1QL Limit pushdown sometimes causing Query to return less results when using TTL

Request

Make indexer aware of expiring documents

Problem

When using an index for the query (for the population), and later a fetch, you might get 0 results, even thought there is a documents which supposed to be returned. that because they have been TTLed and the index was not notified about it.

Query:

Select name, data_field

from myBucket

where type = "test"

limit 10

create index ix_1 on test(name)

Put a random TTL on documents -> results, even thought you requested 10 documents, sometimes you wouldn't get 10 but less.

+Backgroun+d

Currently KV supports TTL - but doesn't report it as a mutation (also to the Indexer) up until the expiry pager was run or the document has been accessed.