Yep. Almost! Changing the default in a minor version might break some scripts/tooling that manipulate schema and potentially create new MVs (as dangerous as it currently is - manipulating schema in that way), and that would still not be very nice.
Introducing a flag and leaving it at false in a minor is harmless. — AY On 4 October 2017 at 18:24:16, Stefan Podkowinski (s...@apache.org) wrote: If "disabling a feature" is just about preventing some CQL from execution along with a warning log message, I'm fine with that. But if that's being the case, I don't really understand why making this change in a minor version would be a problem, since existing MVs wouldn't be affected anyways and should just work as before, even with the enabled flag set to false.
