Hi, we deployed presto based on the helm file. It ...
# troubleshooting
a
Hi, we deployed presto based on the helm file. It seems like offset is not enabled. Any idea how to enable offset?
k
@Haitao Zhang
h
@Xiang Fu has more knowledge about the helm chart
x
what is offset you are mentioning to?
a
Hi, when using offset num1 limit num2 in presto query, it returned Offset support is not enabled. presto:default> select * from table_name offset 10 limit 10; Query 20220516_231652_00449_7gh97 failed: Offset support is not enabled
x
oh, use limit 10,10
also pinot doesn’t support offset without ordering
so just select * won’t give you consist results
why you need offset 10?
a
Hi, it’s presto query that returned offset not enabled. Need offset for pagination.
x
Yeah, check presto query syntax
Note that pagination is not enabled
So the results is not stable
Better to fetch enough rows and cache from front-end
a
👌
Thanks.
x
btw, offset is a session config
you can enable it by setting session config
offset_clause_enabled
a
👍
Copy code
Add support for the OFFSET clause in SQL query expressions. This feature can be enabled by setting the session property offset_clause_enabled or configuration property offset-clause-enabled to true.
so I think it’s more like enable it from presto side
though still pinot side won’t give you consistent results
a
Thanks, but will Pinot give consistent results with order by clause?
x
it will, but you pay the cost of sorting for every query
it will be much slow comparing to
select *
a
I see.🙏
x
especially for large data set