Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Correctness - API / Semantic Definition
-
Low
-
Low Hanging Fruit
-
Adhoc Test
-
All
-
None
-
Description
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.