kylin-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shaofeng SHI (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (KYLIN-3434) Support prepare statement in Kylin server side
Date Tue, 14 Aug 2018 09:42:00 GMT

     [ https://issues.apache.org/jira/browse/KYLIN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shaofeng SHI updated KYLIN-3434:
--------------------------------
    Fix Version/s: v2.5.0

> Support prepare statement in Kylin server side
> ----------------------------------------------
>
>                 Key: KYLIN-3434
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3434
>             Project: Kylin
>          Issue Type: Improvement
>          Components: Query Engine
>            Reporter: Ma Gang
>            Assignee: Ma Gang
>            Priority: Major
>             Fix For: v2.5.0
>
>
> Kylin use calcite as sql engine, when a sql comes to Kylin server, it requires to be
parsed, optimized, code gen, and then query Kylin's cube storage, the previous 3 steps often
take 50-150 ms to complete(depends on the complexity of the sql). If we support to cache
the parsed result in Kylin server, the 3 steps will be saved.
> The idea is to cache calcite's PreparedStatement object and related OLAPContexts in the
server side, when the prepare request comes with the same sql, reuse the PreparedStatement
to do the execution. Since the PreparedStatement is not thread safe, so I planned to use
ObjectPool to cache the PreparedStatement.(use apache commons-pool lib)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message