You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@kylin.apache.org by "albertoramon (JIRA)" <ji...@apache.org> on 2018/07/05 05:18:00 UTC

[jira] [Comment Edited] (KYLIN-3434) Support prepare statement in Kylin server side

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

albertoramon edited comment on KYLIN-3434 at 7/5/18 5:17 AM:
-------------------------------------------------------------

Is the same or related?

KYLIN-2001 

KYLIN-189


was (Author: albertoramon):
Is the same? KYLIN-2001

> Support prepare statement in Kylin server side
> ----------------------------------------------
>
>                 Key: KYLIN-3434
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3434
>             Project: Kylin
>          Issue Type: Improvement
>            Reporter: Ma Gang
>            Assignee: Ma Gang
>            Priority: Major
>
> 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)