[
https://issues.apache.org/jira/browse/CASSANDRA-17498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17514312#comment-17514312
]
Josh McKenzie edited comment on CASSANDRA-17498 at 3/29/22, 8:08 PM:
---------------------------------------------------------------------
Technically yes. The UX of "max of 0" is slightly less clear than "is this
feature enabled or disabled", and the overhead of adding another guardrail in
terms of complexity in the codebase is quite small so I'm in favor of adding
the formal toggle personally.
edit: I'd also add - secondary indexes are one of those features we've said for
a long time are "only use this if you really know what you're doing and aren't
going to need to scale". So that's another check in the box of making it a
formal parameter that people can straight disable across the board I think.
Open to alternative viewpoints as always though.
was (Author: jmckenzie):
Technically yes. The UX of "max of 0" is slightly less clear than "is this
feature enabled or disabled", and the overhead of adding another guardrail in
terms of complexity in the codebase is quite small so I'm in favor of adding
the formal toggle personally.
> Add Guardrail to disallow creation of secondary indexes
> -------------------------------------------------------
>
> Key: CASSANDRA-17498
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17498
> Project: Cassandra
> Issue Type: New Feature
> Components: Feature/Guardrails
> Reporter: Josh McKenzie
> Priority: Normal
>
> Rather than just a min/max on secondary indexes, we should also have the
> ability to completely enable or disable creation of secondary indexes via
> guardrails.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
