[
https://issues.apache.org/jira/browse/KYLIN-3434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16529695#comment-16529695
]
ASF GitHub Bot commented on KYLIN-3434:
---------------------------------------
asfgit commented on issue #160: KYLIN-3434 Support prepare statement in Kylin
server side
URL: https://github.com/apache/kylin/pull/160#issuecomment-401759058
Can one of the admins verify this patch?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> 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)
