| I first stumbled a bit with "there's no where clause and no filtering
allowed…"
| But I doubt that reaction from any experienced cql user will last more
than a moment.
I was also wondering about that, but this syntax looks good. More
importantly, it will be easy to explain to end users.
Patrick
On Tue, May 23, 2023 at 1:28 PM Jonathan Ellis <jbel...@gmail.com> wrote:
> Yes, that's totally reasonable syntactically, but I'd prefer not to open
> the can of worms of ordering by some functions but not others (and I
> definitely don't want to try to tackle ordering by all functions). "You
> can order by expressions involving SAI columns" is a pretty easy rule to
> explain.
>
> On Tue, May 23, 2023 at 12:53 PM David Capwell <dcapw...@apple.com> wrote:
>
>> I am ok with the syntax, but wondering if a function maybe better than a
>> CQL change?
>>
>> SELECT id, start, end, text
>> FROM {self.keyspace}.{self.table}
>> ORDER BY ANN(embedding, ?)
>> LIMIT ?
>>
>> Not really a common syntax, but could be useful down the line
>>
>> On May 23, 2023, at 12:37 AM, Mick Semb Wever <m...@apache.org> wrote:
>>
>>
>>> *I propose that we adopt `ORDER BY` syntax, supporting it for vector
>>> indexes first and eventually for all SAI indexes. So this query would
>>> become SELECT id, start, end, text FROM
>>> {self.keyspace}.{self.table} ORDER BY embedding ANN OF %s LIMIT %s*
>>>
>>
>>
>> LGTM.
>>
>> I first stumbled a bit with "there's no where clause and no filtering
>> allowed…"
>>
>> But I doubt that reaction from any experienced cql user will last more
>> than a moment.
>>
>>
>>
>
> --
> Jonathan Ellis
> co-founder, http://www.datastax.com
> @spyced
>
