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

Posted to issues-all@impala.apache.org by "Steve Carlin (Jira)" <ji...@apache.org> on 2026/04/11 00:10:00 UTC

[jira] [Resolved] (IMPALA-14408) Calcite Planner: server flag should run Calcite through JniFrontend

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

Steve Carlin resolved IMPALA-14408.
-----------------------------------
    Resolution: Fixed

> 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: issues-all-unsubscribe@impala.apache.org
For additional commands, e-mail: issues-all-help@impala.apache.org