[ 
https://issues.apache.org/jira/browse/CASSANDRA-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16759926#comment-16759926
 ] 

Andrés de la Peña commented on CASSANDRA-14866:
-----------------------------------------------

I've updated the patch to disable both {{enable_materialized_views}} and 
{{enable_sasi_indexes}} by default in trunk, as discussed in the mail list:
||[3.11|https://github.com/adelapena/cassandra/tree/CASSANDRA-14866-3.11]||[trunk|https://github.com/adelapena/cassandra/tree/CASSANDRA-14866-trunk]||[dtest|https://github.com/adelapena/cassandra-dtest/commits/CASSANDRA-14866]||

I've moved {{enable_materialized_views}}, {{enable_sasi_indexes}} and 
{{enable_transient_replication}} to an experimental features section in 
cassandra.yaml.

Each dtest creating materialized views is modified to activate the flag, I 
don't know if there is a better way to do this.

> Issue a CQL native protocol warning if SASI indexes are enabled on a table
> --------------------------------------------------------------------------
>
>                 Key: CASSANDRA-14866
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-14866
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Feature/SASI
>            Reporter: Andrés de la Peña
>            Assignee: Andrés de la Peña
>            Priority: Major
>             Fix For: 4.0, 3.11.x, 4.x
>
>
> If someone enables SASI indexes then we should return a native protocol 
> warning that will be printed by cqlsh saying that they are beta quality still 
> and you need to be careful with using them in production.
> This is motivated not only by [the existing bugs and 
> limitations|https://issues.apache.org/jira/browse/CASSANDRA-12674?jql=project%20%3D%20CASSANDRA%20AND%20status%20%3D%20Open%20AND%20component%20%3D%20sasi]
>  but for the fact that they haven't been extensively tested yet.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to