[
https://issues.apache.org/jira/browse/HIVE-11531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sergey Shelukhin updated HIVE-11531:
------------------------------------
Description: For any UIs that involve pagination, it is useful to issue
queries in the form SELECT ... LIMIT X,Y where X,Y are coordinates inside the
result to be paginated (which can be extremely large by itself). At present,
ROW_NUMBER can be used to achieve this effect, but optimizations for LIMIT such
as TopN in ReduceSink do not apply to ROW_NUMBER. We can add first class
support for "skip" to existing limit, or improve ROW_NUMBER for better
performance (was: For any UIs that involve pagination, it is useful to issue
queries in the form SELECT ... LIMIT X,Y where X,Y are coordinates inside the
paginated results (which can be extremely large by itself). At present,
ROW_NUMBER can be used to achieve with effect, but optimizations for LIMIT such
as TopN in ReduceSink do not apply to ROW_NUMBER. We can add first class
support for "skip" to existing limit, or improve ROW_NUMBER for better
performance)
> Add mysql-style LIMIT support to Hive, or improve ROW_NUMBER performance-wise
> -----------------------------------------------------------------------------
>
> Key: HIVE-11531
> URL: https://issues.apache.org/jira/browse/HIVE-11531
> Project: Hive
> Issue Type: Improvement
> Reporter: Sergey Shelukhin
>
> For any UIs that involve pagination, it is useful to issue queries in the
> form SELECT ... LIMIT X,Y where X,Y are coordinates inside the result to be
> paginated (which can be extremely large by itself). At present, ROW_NUMBER
> can be used to achieve this effect, but optimizations for LIMIT such as TopN
> in ReduceSink do not apply to ROW_NUMBER. We can add first class support for
> "skip" to existing limit, or improve ROW_NUMBER for better performance
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
