OK… I think concept of hash range distribution across tablets is same, irrespective of using YCQL or YSQL on yugabyteDB
why hash ranges in this querylink looking different than below range?
In the querylink, I was expecting four rows only in system.partitions table, because there are four tablet servers in central region, as shown below
Tablet 1 hash range [0,16384)
Tablet 2 hash range [16384, 32768)
Tablet 3 hash range [32768, 49152)
Tablet 4 hash range [49152, 65535]