[
https://issues.apache.org/jira/browse/IMPALA-14408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18039839#comment-18039839
]
ASF subversion and git services commented on IMPALA-14408:
----------------------------------------------------------
Commit e67b627858bf0c404fd041709a9ce8577085ac99 in impala's branch
refs/heads/master from Steve Carlin
[ https://gitbox.apache.org/repos/asf?p=impala.git;h=e67b62785 ]
IMPALA-14408: (addendum) Log Calcite exception in profile
This addendum logs the exception thrown in the runtime profile
under the CalciteFailureReason key.
Testing: test_ranger.py uses this.
Change-Id: Ia18a52c488f9c73d51690997b277fd8e918c645f
Reviewed-on: http://gerrit.cloudera.org:8080/23686
Reviewed-by: Joe McDonnell <[email protected]>
Tested-by: Impala Public Jenkins <[email protected]>
> Calcite Planner: server flag should run Calcite through JniFrontend
> -------------------------------------------------------------------
>
> Key: IMPALA-14408
> URL: https://issues.apache.org/jira/browse/IMPALA-14408
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Priority: Major
>
> Currently, there is a server flag option "use_calcite_planner" which routes
> queries into the CalciteJniFrontend class instead of the JniFrontend class.
> CalciteJniFrontend does not support all Impala features and needs to be
> removed. All Calcite queries should go through the normal JniFrontend path.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
