JMAP search: can we know when the external index is caught up?

[julien]

Thanks, this was very helpful.

We tested it on 0.16.14. x:Task/query and x:Task/get work with a scoped API key, and the IndexDocument tasks include accountId.

One small difference: filtering x:Task/query directly by accountId returned unsupportedFilter for us. So for now we have to query the task set and filter by account on our side.

We also created the mixed-filter relevance request here:

Keep relevance order when Email/query mixes text and local filters

Hi, following up from this thread: For our search use case we almost always combine a text query with mailbox, keyword or ACL filters. As you explained, when every filter can go to the external search engine the results keep relevance order. But when local filters are mixed in, the merge ends up in document id order. This makes the best text match not necessarily first. Would it be possible for that merge step to keep the order returned by the external engine, and only remove docs that don’…

Thanks again.