When performing a search query, the documentation for all SDKs only reference a scan consistency of ‘not bounded’, which is the default I believe. Is ‘request plus’ not implemented on the server side yet or has it been forgotten in the SDKs ?
not_bounded is the default. We also support at_plus where the user will have to provide in the request a vector of sequence numbers/vb uuids as constraints to meet before the search is executed - this is the only support for Read-Your-Own-Writes we accommodate at the moment.
request_plus is not supported for search indexes at the moment.
Ok so you can pass some mutation tokens but not request_plus, correct ?
Is it scheduled to implement request_plus in the coming versions or is it not in the foreseable future ?
There is a plan for it, the date when we’ll put it out hasn’t been finalized just yet though.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.