[
https://issues.apache.org/jira/browse/KYLIN-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14679483#comment-14679483
]
liyang commented on KYLIN-742:
------------------------------
If Hive or SparkSQL does not support 'offset', then you are out of luck.
My general suggestion about pagination is try cache enough records in the
frontend, and avoid going to SQL engine like Kylin or Hive as much as possible
(even they support offset+limit). It's for performance sake. In big data
analysis, query is very expensive. It unwise to call backend many times just
for the ease of pagination.
> Route unsupported queries to SparkSQL
> -------------------------------------
>
> Key: KYLIN-742
> URL: https://issues.apache.org/jira/browse/KYLIN-742
> Project: Kylin
> Issue Type: New Feature
> Components: Query Engine, SparkSQL
> Reporter: Luke Han
> Assignee: liyang
> Fix For: Backlog
>
> Attachments: Design Documentation.pdf
>
>
> When Kylin can't serve coming SQL, it will be better to route it to enabled
> SQL on Hadoop like SparkSQL and execute there.
> Then get result and return to client through Kylin server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
