The ordered pagination feature of the read-only analysis engine can solve the problem of unstable pagination query results caused by duplicate field values of the order by clause during parallel data queries. This document describes how to use the ordered pagination feature. For a detailed feature introduction, see Paging Order Preservation Capability. Ordered Pagination Scenarios
Only the limit operator is used, and no order by operator is used.
Duplicate order by keys exist, and only some fields in the output result are sorted.
The subquery involves sorting, but sorting is not performed in the outer query.
Usage Instructions
Enable the ordered pagination feature globally.
Use the feature of setting instance parameters to modify the parameter libra_preserve_order_for_pagination of the read-only analysis engine. The default value of this parameter is OFF. You can set the value to ON to enable the ordered pagination feature for the entire instance. Note:
The ordered pagination feature performs implicit sorting on the output results of queries by default. Therefore, it may cause performance degradation in scenarios with large result sets. It is recommended to specify to use the ordered pagination feature in SQL statements that require this feature.
Enable the ordered pagination feature in a session.
Specify session-level parameters after you log in to the read-only analysis engine to enable/disable the ordered pagination feature in the current session.
mysql> set libra_preserve_order_for_pagination=on;
mysql> set libra_preserve_order_for_pagination=off;
Specify to use the ordered pagination feature during SQL execution.
When a SQL statement is executed, add a hint to specify this SQL statement to use the ordered pagination feature.
Note:
If you use the MySQL client to access the read-only analysis engine, add the -c parameter. Otherwise, the settings of using the ordered pagination feature during SQL execution cannot take effect.
mysql> select t1.c1, t1.c2 from t1, t2 where t1.c1 = t2.c1 order by t1.c1 limit 10,10;