Re: Warn about SASI usage and allow to disable them

2019-01-26 Thread Andrés de la Peña
I agree with Paulo's proposal. I think it will give us a very desirable homogeneity in how we deal with experimental features. I'm +1 to warning, config property, and experimental features (SASI and MV) disabled by default in trunk. These are the explicit votes for now, if I'm counting right: -

Re: Warn about SASI usage and allow to disable them

2019-01-16 Thread Andrés de la Peña
: > > >> > > >> +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

Re: Warn about SASI usage and allow to disable them

2019-01-14 Thread Andrés de la Peña
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 < > a.penya.gar...@gmail.com> > wrote: > > > Hello all, > > > > It is my unde

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