> 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.
We wouldn't have even advanced it to this point if we didn't have copious amounts of (not all public, I know, working on it) evidence it did for the vast majority of workloads. Having said that, I don't strongly agree that we should make it the default in 5.0, because performance isn't the only concern. (correctness, DDL back-compat, which we've sort of touched w/ the YAML default option, etc.) This conversation is now going in like 3 different directions, or at least 3 different "packages" of ideas, so there isn't even a single thing to vote on. Let me read through again and try to distill into something that we might be able to do so with... On Fri, May 12, 2023 at 7:56 AM Aleksey Yeshchenko <alek...@apple.com> wrote: > This. > > I would also consider adding CREATE LEGACY INDEX syntax as an alias for > today’s CREATE INDEX, the latter to be deprecated and (in very distant > future) removed. > > On 12 May 2023, at 13:14, Benedict <bened...@apache.org> wrote: > > 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. > > >
