[ https://issues.apache.org/jira/browse/CASSANDRA-19544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17835520#comment-17835520 ]
Michael Semb Wever edited comment on CASSANDRA-19544 at 4/10/24 6:54 AM: ------------------------------------------------------------------------- Both changes applied (to both patches). CI - 5.0 [^CASSANDRA-19544_50_43_ci_summary.html] , [^CASSANDRA-19544_50_43_results_details.tar.xz] - trunk …wip was (Author: michaelsembwever): Both changes applied (to both patches). > Vector search should be able to restrict on clustering keys when filtering > isn't required > ----------------------------------------------------------------------------------------- > > Key: CASSANDRA-19544 > URL: https://issues.apache.org/jira/browse/CASSANDRA-19544 > Project: Cassandra > Issue Type: Bug > Components: Feature/Vector Search > Reporter: Michael Semb Wever > Assignee: Michael Semb Wever > Priority: Normal > Fix For: 5.0.x, 5.x > > Attachments: CASSANDRA-19544_50_43_ci_summary.html, > CASSANDRA-19544_50_43_results_details.tar.xz, > CASSANDRA-19544_50_ci_summary.html, > CASSANDRA-19544_50_results_details.tar.xz, > CASSANDRA-19544_trunk_ci_summary.html, > CASSANDRA-19544_trunk_results_details.tar.xz > > > With a table that has {{primary key((a,b),c,d)}} > a restriction on only the partition works, > e.g. {{where a=. and b=. order by . ann of .}} > but a restriction that also includes a forward sequence of clustering keys > (i.e. a clustering key restriction that wouldn't require filtering) does not > currently work. > e.g. {{where a=. and b=. and c=. order by . ann of .}} > It appears that StatementRestriction:321 is a little too greedy. -- This message was sent by Atlassian Jira (v8.20.10#820010) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org