At the moment, the dvv_enabled property is missing from the configurable default bucket properties, à la buckets.default.X. This means that users cannot use DVVs by default in their clusters, which forces them to set dvv_enabled to true in every bucket type/bucket in which they want to use them. This strikes me as an unnecessary barrier to DVV usage, which we recommend for most scenarios.
At the moment, the
dvv_enabled
property is missing from the configurable default bucket properties, à labuckets.default.X
. This means that users cannot use DVVs by default in their clusters, which forces them to setdvv_enabled
totrue
in every bucket type/bucket in which they want to use them. This strikes me as an unnecessary barrier to DVV usage, which we recommend for most scenarios.