Re: [DISCUSS] Feature branch version hygiene

...otherwise I'm fine w/ just the CEP name, like "CEP-7" for SAI, etc. On Wed, May 17, 2023 at 11:24 PM Caleb Rackliffe wrote: > So when a CEP slips, do we have to create a 5.1-cep-N? Could we just have > a version that's "NextMajorRelease" or something like that? It should still > be pretty eas

Re: [DISCUSS] Feature branch version hygiene

So when a CEP slips, do we have to create a 5.1-cep-N? Could we just have a version that's "NextMajorRelease" or something like that? It should still be pretty easy to bulk replace if we have something else to filter on, like belonging to an epic? On Wed, May 17, 2023 at 6:42 PM Mick Semb Wever w

Re: [DISCUSS] Feature branch version hygiene

On Tue, 16 May 2023 at 13:02, J. D. Jordan wrote: > Process question/discussion. Should tickets that are merged to CEP feature > branches, like https://issues.apache.org/jira/browse/CASSANDRA-18204, have > a fixver of 5.0 on them After merging to the feature branch? > > > For the SAI CEP which i

Re: [DISCUSS] The future of CREATE INDEX

> 1. What's up with naming anything "legacy". Calling the current index type "2i" seems perfectly fine with me. From what I've heard it can work great for many users? We can give the existing default secondary index any public-facing name we like, but "2i" is too broad. It just stands for "seconda

Re: [DISCUSS] The future of CREATE INDEX

I have read the thread but chose to reply to the top message... I'm coming to this with the background of having worked with MySQL, where both the storage engine and index implementation had many options, and often of course some index types were only available in some engines. I would humbly sug

Re: CEP-30: Approximate Nearest Neighbor(ANN) Vector Search via Storage-Attached Indexes

Thanks for the update, LGTM > On May 17, 2023, at 5:35 AM, Jasonstack Zhao Yang > wrote: > > Hi, > > I have updated the CEP with some details about distributed queries in the > Approach section. > > David: > > > given results have a real ranking, the current 2i logic may yield incorrect >

Re: CEP-30: Approximate Nearest Neighbor(ANN) Vector Search via Storage-Attached Indexes

Hi, I have updated the CEP with some details about distributed queries in the *Approach* section. David: > given results have a real ranking, the current 2i logic may yield incorrect results C* internal iterators are all in primary key order. So we need two in-memory top-k filters, one at repli