Re: [DISCUSS] The future of CREATE INDEX

[Benedict]

This creates huge headaches for everyone successfully using 2i today though, and SAI *is not* guaranteed to perform as well or better - it has a very different performance profile. I think we should deprecate CREATE INDEX, and introduce new syntax CREATE LOCAL INDEX to make clear that this is not a global index, and that this should require the USING syntax to avoid this problem in future.  We should report warnings to the client when CREATE INDEX is used, indicating it is deprecated. On 12 May 2023, at 13:10, Mick Semb Wever <m...@apache.org> wrote:  On Thu, 11 May 2023 at 05:27, Patrick McFadin <pmcfa...@gmail.com> wrote: Having pulled a lot of developers out of the 2i fire, Yes.  I'm keen not to leave 2i as the default once SAI lands. Otherwise I agree with the deprecated first principle, but 2i is just too problematic. Just having no default in 5.0, forcing the user to evaluate which index to use would be an improvement. For example, if the default index in cassandra.yaml option exists but is commented out, that would prevent `CREATE INDEX` from working without specifying a `USING`. Then the yaml documentation would be clear about choices.  I'd be ok with that for 5.0, and then make sai the default in the following release. Note, having the option in cassandra.yaml is problematic, as this is not a per-node setting (AFAIK).