>>> Instead of ripping it out, we could instead disable them in the yaml
>>> with big fat warning comments around it. 


FYI we have already disabled use of materialized views, SASI, and transient 
replication by default in 4.0

https://github.com/apache/cassandra/blob/trunk/conf/cassandra.yaml#L1393

> On Jun 30, 2020, at 6:53 PM, joshua.mcken...@gmail.com wrote:
> 
> I followed up with the clarification about unit and dtests for that reason 
> Dinesh. We test experimental features now.
> 
> If we’re talking about adding experimental features to the 40 quality testing 
> effort, how does that differ from just saying “we won’t release until we’ve 
> tested and stabilized these features and they’re no longer experimental”?
> 
> Maybe I’m just misunderstanding something here?
> 
>> On Jun 30, 2020, at 7:12 PM, Dinesh Joshi <djo...@apache.org> wrote:
>> 
>> 
>>> 
>>>> On Jun 30, 2020, at 4:05 PM, Brandon Williams <dri...@gmail.com> wrote:
>>> 
>>> Instead of ripping it out, we could instead disable them in the yaml
>>> with big fat warning comments around it.  That way people already
>>> using them can just enable them again, but it will raise the bar for
>>> new users who ignore/miss the warnings in the logs and just use them.
>> 
>> Not a bad idea. Although, the real issue is that users enable MV on a 3 node 
>> cluster with a few megs of data and conclude that MVs will horizontally 
>> scale with the size of data. This is what causes issues for users who 
>> naively roll it out in production and discover that MVs do not scale with 
>> their data growth. So whatever we do, the big fat warning should educate the 
>> unsuspecting operator.
>> 
>> Dinesh
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 

Reply via email to