Read concern for "aggregation" metrics is same as configured search read concern · Issue #2163 · eclipse-ditto/ditto · GitHub
More Web Proxy on the site http://driver.im/
You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that for the new aggregation based metrics the used MongoDB readConcern is the same as the configured one for all searches in Ditto.
This can be unwanted, e.g. when having configured a really "costly" readConcern like linearizable in order to guarantee a strong consistency of search results.
For aggregations, the readConcern should be local IMO - the cheapest possible.
Maybe making it configurable is the best way to fix that.
The text was updated successfully, but these errors were encountered:
I noticed that for the new aggregation based metrics the used MongoDB
readConcern
is the same as the configured one for all searches in Ditto.This can be unwanted, e.g. when having configured a really "costly" readConcern like
linearizable
in order to guarantee a strong consistency of search results.For aggregations, the readConcern should be
local
IMO - the cheapest possible.Maybe making it configurable is the best way to fix that.
The text was updated successfully, but these errors were encountered: