The team is working on the definitions of how queries should work with respect to data changes and a future release should cover what you’re looking for. To my knowledge, DP3 doesn’t have the options you need at the moment.
One option that I’ve not tried, but may be pretty elegant given the enhancements in Couchbase Server 3.0, would be to run it and modify N1QL’s source to always do a stale=false view query. This would be a workaround, but not a bad one given the enhancement in view performance in Couchbase Server 3.0.
I was recommending you change the source to N1QL to implement this as a workaround. While the future can change, as of this writing it looks from the issue tracker that this is targeted to DP4 in MB-10944.
I waited for DP4 and unfortunately nothing has been changed.
So can you explain me in details, how i can modify N1QL source ?
…I don’t know how to do this “modify N1QL’s source to always do a stale=false view query.”
Hi, the issue MB-10944 is fixed and is part of the upcoming release and it is part of the code already. Could you explain why you need stale=false all the time? N1QL does provide a large set of options for consistency and there may be other options that could help you satify the requirement without taking the ‘strict-consistency’ hit.