[
https://issues.apache.org/jira/browse/KYLIN-742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14900256#comment-14900256
]
Murali Krishna edited comment on KYLIN-742 at 9/21/15 6:32 AM:
---------------------------------------------------------------
Minor update in the design, since the calicite-core source has undergone
significant updates with respect to the package conventions, the exceptions
mentioned in the design document [1] are not available in the versions of the
jar used at present (1.3.0-incubating). Instead the exception will be of type -
org.apache.calcite.sql.parser.SqlParseException and
org.apache.calcite.sql.validate.SqlValidatorException respectively.
[1]
https://issues.apache.org/jira/secure/attachment/12744202/Design%20Documentation.pdf
was (Author: murkrishn):
Minor update in the design, since the calicite-core source has undergone a
significant updates with respect to the package conventions, the exceptions
mentioned in the design document [1] are not available in the versions of the
jar used at present (1.3.0-incubating). Instead the exception will be of type -
org.apache.calcite.sql.parser.SqlParseException and
org.apache.calcite.sql.validate.SqlValidatorException respectively.
[1]
https://issues.apache.org/jira/secure/attachment/12744202/Design%20Documentation.pdf
> Route unsupported queries to SparkSQL
> -------------------------------------
>
> Key: KYLIN-742
> URL: https://issues.apache.org/jira/browse/KYLIN-742
> Project: Kylin
> Issue Type: New Feature
> Components: Query Engine, SparkSQL
> Reporter: Luke Han
> Assignee: liyang
> Fix For: Backlog
>
> Attachments: 1.x-HBase1.x-KYLIN-742-update.patch,
> 1.x-HBase1.x-KYLIN-742-with-review-comments-#1-update-21_09_2015.patch,
> Design Documentation.pdf
>
>
> When Kylin can't serve coming SQL, it will be better to route it to enabled
> SQL on Hadoop like SparkSQL and execute there.
> Then get result and return to client through Kylin server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
