At first I wasn’t sure about using ORDER BY, but the more I think about what is
actually going on, I think it does make sense.
This also matches up with some ideas that have been floating around about being
able to ORDER BY a sorted SAI index.
-Jeremiah
> On May 22, 2023, at 2:28 PM, Jonathan
| 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
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.
O
I'll hold off on this until Alex Petrov chimes in. @Alex -> got any thoughts
here?
On Tue, May 16, 2023, at 5:17 PM, Jeremy Hanna wrote:
> I think it would be great to onboard Harry more officially into the project.
> However it would be nice to perhaps do some sanity checking outside of Apple
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 wr
>
>
> *I propose that we adopt `ORDER BY` syntax, supporting it for vector
> indexes first and eventually for all SAI indexes. So this query would
> becomeSELECT id, start, end, text FROM
> {self.keyspace}.{self.table} ORDER BY embedding ANN OF %s LIMIT %s*
>
LGTM.
I first stumb
