It's confusing with PQS in the mix :)
The original documentation meant client side (JDBC thick driver) and
server-side (HBase). With PQS in the mix, you'd need PQS and HBase (but
not client-side, guessing).
On 5/24/18 3:24 AM, Stepan Migunov wrote:
Yes, I read this. But the document says
OFFSET will not scale well with large values as there is no way to
implement it in HBase other than scanning from the beginning and skipping
that many rows. I'd suggest using row value constructors instead. You can
read more about that here: https://phoenix.apache.org/paged.html
Thanks,
James
On
Hi everyone.
I faced the problem of executing query. We have table with 150 rows, if you
try execute query with huge offset, order by and using limit, phoenix will be
crushed with such problem:
Example query:
Select * from table order by col1 , col2 limit 1000 offset 15677558;
Caused
