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

**URL:** <https://forum.yugabyte.com/t/invalid-arguments-all-hash-columns-must-be-set-if-order-by-clause-is-present/778>\
**Category:** General\
**Created:** [July 22, 2020, 8:29pm UTC](https://forum.yugabyte.com/t/invalid-arguments-all-hash-columns-must-be-set-if-order-by-clause-is-present/778 "2020-07-22T20:29:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![dorian\_yugabyte](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.yugabyte.com/dorian_yugabyte/32/206_2.png) [@dorian\_yugabyte](https://forum.yugabyte.com/u/dorian_yugabyte)\
**Post date:** [July 23, 2020, 9:59am UTC](https://forum.yugabyte.com/t/invalid-arguments-all-hash-columns-must-be-set-if-order-by-clause-is-present/778/2 "2020-07-23T09:59:30Z")

</div>

Hi @Vlad_Koretsky

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](https://docs.yugabyte.com/latest/api/ycql/dml_select/#order-by-clause).

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

---

_[View the full topic](https://forum.yugabyte.com/t/invalid-arguments-all-hash-columns-must-be-set-if-order-by-clause-is-present/778)._