> CDC sounds like it is in the same basket, but it already has the > `cdc_enabled` yaml flag which defaults false.
I went this route because I was incredibly wary of changing the CL code and wanted to shield non-CDC users from any and all risk I reasonably could. I don't know of any outstanding issues with the feature, and this calls into question how we distinguish between 'new feature, we consider this stable (scope is constrained, testing coverage, etc)', and 'new feature, this is admittedly experimental', as well as determining how long something remains 'experimental' and at what point we remove that .yaml gate-keeping and warning. For instance, SASI hasn't seen that much development in a long while, so at what point do we address Marcus' question of 'when do we consider an experimental feature atrophied and remove it'? What does this mean for users that took the plunge and are using these features in production if they're stable for their use-case? We're also going to introduce complexity and risk into the code-base w/experimental features we later pull out. With as much static state as we have in this project (and a lot of the design precedent in the code-base, inheritance coupling, etc), you can't exactly add a completely isolated, cleanly abstracted feature into the code-base and remove it risk-free later. On Mon, Oct 2, 2017 at 7:16 PM, Mick Semb Wever <m...@thelastpickle.com> wrote: > On 3 October 2017 at 04:57, Aleksey Yeshchenko <alek...@apple.com> wrote: > >> The idea is to check the flag in CreateViewStatement, so creation of new >> MVs doesn’t succeed without that flag flipped. >> Obviously, just disabling existing MVs working in a minor would be silly. >> As for the warning - yes, that should also be emitted. Unconditionally. >> > > > Thanks Aleksey, this was the best read in this thread imo of what should be > done with MVs. > (With these warnings being emitted in both logs and cqlsh). > > Hopefully similar "creation flags" and log+cqlsh warnings can be added to: > triggers, SASI, and incremental repair (<4.0). > > CDC sounds like it is in the same basket, but it already has the > `cdc_enabled` yaml flag which defaults false. > > Mick --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
