> > [POLL] Centralize existing syntax or create new syntax? > > 1.) CREATE INDEX ... USING .... WITH OPTIONS... > 2.) CREATE LOCAL INDEX ... USING ... WITH OPTIONS... (same as 1, but > adds LOCAL keyword for clarity and separation from future GLOBAL indexes) >
1.) CREATE INDEX ... USING .... WITH OPTIONS... [POLL] Should there be a default? (YES/NO) > Yes [POLL] What do do with the default? > > 1.) Allow a default, and switch it to SAI (no configurables) > 2.) Allow a default, and stay w/ the legacy 2i (no configurables) > 3.) YAML config to override default index (legacy 2i remains the default) > 4.) YAML config/guardrail to require index type selection (not required by > default) > 3.) YAML config to override default index (legacy 2i remains the default) On Mon, 15 May 2023 at 08:54, Mick Semb Wever <m...@apache.org> wrote: > > > [POLL] Centralize existing syntax or create new syntax? >> >> 1.) CREATE INDEX ... USING .... WITH OPTIONS... >> 2.) CREATE LOCAL INDEX ... USING ... WITH OPTIONS... (same as 1, but >> adds LOCAL keyword for clarity and separation from future GLOBAL indexes) >> > > > (1) CREATE INDEX … > > > >> [POLL] Should there be a default? (YES/NO) >> > > > Yes (but see below). > > > >> [POLL] What do do with the default? >> >> 1.) Allow a default, and switch it to SAI (no configurables) >> 2.) Allow a default, and stay w/ the legacy 2i (no configurables) >> 3.) YAML config to override default index (legacy 2i remains the default) >> 4.) YAML config/guardrail to require index type selection (not required >> by default) >> > > > (4) YAML config. Commented out default of 2i. > > I agree that the default cannot change in 5.0, but our existing default of > 2i can be commented out. > > For the user this gives them the same feedback, and puts the same > requirement to edit one line of yaml, as when we disabled MVs and SASI in > 4.0 > No one has complained about either of these, which is a clear signal folk > understood how to get their existing DDLs to work from 3.x to 4.x > -- [image: DataStax Logo Square] <https://www.datastax.com/> *Mike Adamson* Engineering +1 650 389 6000 <16503896000> | datastax.com <https://www.datastax.com/> Find DataStax Online: [image: LinkedIn Logo] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_company_datastax&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU&m=uHzE4WhPViSF0rsjSxKhfwGDU1Bo7USObSc_aIcgelo&s=akx0E6l2bnTjOvA-YxtonbW0M4b6bNg4nRwmcHNDo4Q&e=> [image: Facebook Logo] <https://urldefense.proofpoint.com/v2/url?u=https-3A__www.facebook.com_datastax&d=DwMFaQ&c=adz96Xi0w1RHqtPMowiL2g&r=IFj3MdIKYLLXIUhYdUGB0cTzTlxyCb7_VUmICBaYilU&m=uHzE4WhPViSF0rsjSxKhfwGDU1Bo7USObSc_aIcgelo&s=ncMlB41-6hHuqx-EhnM83-KVtjMegQ9c2l2zDzHAxiU&e=> [image: Twitter Logo] <https://twitter.com/DataStax> [image: RSS Feed] <https://www.datastax.com/blog/rss.xml> [image: Github Logo] <https://github.com/datastax>
