[
https://issues.apache.org/jira/browse/CASSANDRA-14866?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16676152#comment-16676152
]
Jeff Jirsa commented on CASSANDRA-14866:
----------------------------------------
Seems like an odd time for this, but other retroactively "experimental"
features came with a way to toggle them off in the yaml rather than a per-user
warning on CQL statements and discussion on the mailing list before they were
committed.
Also, do we REALLY need to send the client warning on {{SELECT}} ? Seems like a
big hammer there.
> 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: 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: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
