You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "Xiaoxiang Yu (Jira)" <ji...@apache.org> on 2021/02/07 14:36:00 UTC
[jira] [Updated] (KYLIN-4905) Support limit .. offset ... in spark
query engine
[ https://issues.apache.org/jira/browse/KYLIN-4905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiaoxiang Yu updated KYLIN-4905:
--------------------------------
Fix Version/s: v4.0.0-GA
> Support limit .. offset ... in spark query engine
> -------------------------------------------------
>
> Key: KYLIN-4905
> URL: https://issues.apache.org/jira/browse/KYLIN-4905
> Project: Kylin
> Issue Type: New Feature
> Components: Query Engine
> Affects Versions: v4.0.0-alpha
> Reporter: ShengJun Zheng
> Priority: Major
> Fix For: v4.0.0-GA
>
>
> when use top-level result offset clause in query expression (ANSI SQL) : limit xxx offset xxx in spark query engine，limit will not push down into spark engine, and offset will not take effect. This is incompatible wIth Kylin 2.x~3.x.
> After looking through the code, i found it's because spark dose not support limit ... offset ... now. There is a spark issue in progress: https://issues.apache.org/jira/browse/SPARK-28330, which was created in 2019 but still in progress.
> So, should we support this feature temporarily in KYLIN? ：
> 1. push down limit to spark
> 2. take result from starting offset in KYLIN query server
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)