Invalid Arguments. All hash columns must be set if order by clause is present

dorian_yugabyte · July 23, 2020, 9:59am

Not specifying the partitioning-columns (id in this case) will result in cluster-wide full table scan and is an anti pattern. See docs SELECT statement [YCQL] | YugabyteDB Docs.

If this is needed, can you open an issue on github ?

Topic		Replies	Views
What is the order of returned columns in a failed IF expression in YCQL General	1	615	January 12, 2021
Does CREATE TABLE syntax need HASH keyword explicitly? General	7	826	May 6, 2022
IF NOT EXISTS clause is not returning all columns, If the row already exists General	1	984	January 12, 2021
What really happen when update and insert data to table with secondary index on regular column General	3	734	May 11, 2020
Invalid argument: Read time should NOT be specified for serializable isolation level General	4	783	November 10, 2022

Invalid Arguments. All hash columns must be set if order by clause is present

Related topics