Will hash partitioning columns be used in query optimization?

["Ray Liu (rayliu)" <ra...@cisco.com>]

For example, I have a table with composite primary key (a,b,c) (in that exact order)  and use b 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 but check the hash bucket for “b=1” for “c=2”.
Is my understanding correct?