You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "hailin.huang (Jira)" <ji...@apache.org> on 2019/11/08 01:27:00 UTC

[jira] [Commented] (KYLIN-4214) Distributed query engine

    [ https://issues.apache.org/jira/browse/KYLIN-4214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16969705#comment-16969705 ] 

hailin.huang commented on KYLIN-4214:
-------------------------------------

Postgre SQL might be another good choice:
- first, spark sql is not enouch stable.
- second, if we import anohter query component, the use maintain cost will increase a lot
- in current Cloud env, new componet means buy more ECS or more service.
PG in my opinion, which is a better:
- we can seperate query service and meta data service from kylin.
- PG is great OLAP engine. and what we should do might like using calcite

> Distributed query engine
> ------------------------
>
>                 Key: KYLIN-4214
>                 URL: https://issues.apache.org/jira/browse/KYLIN-4214
>             Project: Kylin
>          Issue Type: New Feature
>          Components: Query Engine
>            Reporter: yiming.xu
>            Assignee: yiming.xu
>            Priority: Major
>
> Sql through calcite analysis optimization will generate a tree of OLAP rel,
> and spark's catalyst is also generated by parsing SQL after a tree,
> automatically optimized to become a dataframe to calculate, if the plan of
> calcite can be converted into a spark plan, then we will achieve
> distributed computing, calcite is only responsible for parsing SQL and
> returning result sets, reducing the pressure on the kylin server side.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)