Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Jeff Jirsa
+1 on config -0 on warning -0 on disabling by default -- Jeff Jirsa > On Jan 14, 2019, at 9:22 PM, Taylor Cressy wrote: > > +1 on config. +1 on disabling. > > +1 on applying it to materialized views as well. > >> On Jan 14, 2019, at 17:29, Joshua McKenzie wrote: >> >> +1 on config

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Jasonstack Zhao Yang
+1 on yaml config. +1 on disable by default. On Tue, 15 Jan 2019 at 13:23 Taylor Cressy wrote: > +1 on config. +1 on disabling. > > +1 on applying it to materialized views as well. > > > On Jan 14, 2019, at 17:29, Joshua McKenzie wrote: > > > > +1 on config change, +1 on disabling, and so long

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Taylor Cressy
+1 on config. +1 on disabling. +1 on applying it to materialized views as well. > On Jan 14, 2019, at 17:29, Joshua McKenzie wrote: > > +1 on config change, +1 on disabling, and so long as the comments make the > limitations and risks extremely clear, I'm fine w/out the client warning. > >

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Joshua McKenzie
+1 on config change, +1 on disabling, and so long as the comments make the limitations and risks extremely clear, I'm fine w/out the client warning. On Mon, Jan 14, 2019 at 12:28 PM Andrés de la Peña wrote: > I mean disabling the creation of new SASI indices with CREATE INDEX > statement, the

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Andrés de la Peña
I mean disabling the creation of new SASI indices with CREATE INDEX statement, the existing indexes would continue working. The CQL client warning will be thrown with that creation statement as well (if they are enabled). On Mon, 14 Jan 2019 at 20:18, Jeff Jirsa wrote: > When we say disable, do

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Jeff Jirsa
When we say disable, do you mean disable creation of new SASI indices, or disable using existing ones? I assume it's just creation of new? On Mon, Jan 14, 2019 at 11:19 AM Andrés de la Peña wrote: > Hello all, > > It is my understanding that SASI is still to be considered an > experimental/beta

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Brandon Williams
I amend to +1 everything except warning, which I'm +0 on. On Mon, Jan 14, 2019 at 1:59 PM Caleb Rackliffe wrote: > +1 to config and disable > > On Mon, Jan 14, 2019, 1:54 PM Mick Semb Wever > > > > > > > The purpose for this thread is discussing whether we want to add this > > > warning, the

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Caleb Rackliffe
+1 to config and disable On Mon, Jan 14, 2019, 1:54 PM Mick Semb Wever > > > The purpose for this thread is discussing whether we want to add this > > warning, the config property and, more controversially, if we want to set > > SASI as disabled by default in trunk. > > > I'm +1 on everything,

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Mick Semb Wever
> The purpose for this thread is discussing whether we want to add this > warning, the config property and, more controversially, if we want to set > SASI as disabled by default in trunk. I'm +1 on everything, except the warning. I think if we add the config property and it's disabled in

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Brandon Williams
+1 to warn, config, and disable. On Mon, Jan 14, 2019 at 1:45 PM Jonathan Haddad wrote: > I'm very much in favor of a warning, and I lean towards disabling them (and > MVs, while we're at it) by default as well. > > I've seen both features be the death of clusters, and are a major risk for >

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Jonathan Haddad
I'm very much in favor of a warning, and I lean towards disabling them (and MVs, while we're at it) by default as well. I've seen both features be the death of clusters, and are a major risk for teams that are brand new to Cassandra. On Mon, Jan 14, 2019 at 11:19 AM Andrés de la Peña wrote:

Warn about SASI usage and allow to disable them

2019-01-14 Thread Andrés de la Peña
Hello all, It is my understanding that SASI is still to be considered an experimental/beta feature, and they apparently are not being very actively developed. Some higlighted problems in SASI are: - OOMs during flush, as it is described in CASSANDRA-12662 - General secondary index consistency