1. VECTOR<FLOAT,n> 2. VECTOR FLOAT[n] 3. FLOAT[N] (Non null by default)
Redundant or not, I think having the VECTOR keyword helps signify what the app is generally about and helps get buy-in from ML stakeholders. On Thu, May 4, 2023 at 3:45 AM Benedict <bened...@apache.org> wrote: > > Hurrah for initial agreement. > > For syntax, I think one option was just FLOAT[N]. In VECTOR FLOAT[N], VECTOR > is redundant - FLOAT[N] is fully descriptive by itself. I don’t think VECTOR > should be used to simply imply non-null, as this would be very unintuitive. > More logical would be NONNULL, if this is the only condition being applied. > Alternatively for arrays we could default to NONNULL and later introduce > NULLABLE if we want to permit nulls. > > If the word vector is to be used it makes more sense to make it look like a > list, so VECTOR<FLOAT, N> as here the word VECTOR is clearly not redundant. > > So, I vote: > > 1) (NON NULL) FLOAT[N] > 2) FLOAT[N] (Non null by default) > 3) VECTOR<FLOAT, N> > > > > On 4 May 2023, at 08:52, Mick Semb Wever <m...@apache.org> wrote: > > >> >> Did we agree on a CQL syntax? >> >> I don’t believe there has been a pool on CQL syntax… my understanding >> reading all the threads is that there are ~4-5 options and non are -1ed, so >> believe we are waiting for majority rule on this? > > > > Re-reading that thread, IIUC the valid choices remaining are… > > 1. VECTOR FLOAT[n] > 2. FLOAT VECTOR[n] > 3. VECTOR<FLOAT,n> > 4. VECTOR[n]<FLOAT> > 5. ARRAY<FLOAT, n> > 6. NON-NULL FROZEN<FLOAT[n]> > > > Yes I'm putting my preference (1) first ;) because (banging on) if the future > of CQL will have FLOAT[n] and FROZEN<FLOAT[n]>, where the VECTOR keyword is: > for general cql users; just meaning "non-null and frozen", these gel best > together. > > Options (5) and (6) are for those that feel we can and should provide this > type without introducing the vector keyword. > >
