For example, I have a table with composite primary key (a,b,c) (in that exact order) and column b is set as hash partitioning column. If I run a sql query like this select * from table where b = 1 and c = 2
In my understanding, because we already set b as hash partitioning column Kudu will not do a full table scan. Instead Kudu will look for “c=2” in the hash bucket of “b=1”. Is my understanding correct?
