Strongly disagree with MV’s being isolated part. You can feel the touch of the MVs in the read path, write path, metadata handling, whether you use them or not. And comparing any of those before/after MVs were introduced makes me sad every time I face any of it. It made our codebase objectively worse.
On 4 October 2017 at 19:26:43, Josh McKenzie (jmcken...@apache.org) wrote: MV's (and SASI, for example) are fairly well isolated Well, if the developers keep pushing untested complex features onto the project, then refuse to admit their mistakes, then as an operator you *should* think long and hard and you *should* revisit your confidence. Or else you are a shitty operator. On 4 October 2017 at 19:26:43, Josh McKenzie (jmcken...@apache.org) wrote: If I were an operator and built a critical part of my business on a released feature that developers then decided to default-disable as 'experimental' post-hoc, I'd think long and hard about using any new features in that project in the future (and revisit my confidence in all other features I relied on, and the software as a whole). — AY
