[
https://issues.apache.org/jira/browse/IMPALA-14488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Carlin reassigned IMPALA-14488:
-------------------------------------
Assignee: Steve Carlin
> Calcite planner: support fallback to Original planner
> -----------------------------------------------------
>
> Key: IMPALA-14488
> URL: https://issues.apache.org/jira/browse/IMPALA-14488
> Project: IMPALA
> Issue Type: Sub-task
> Reporter: Steve Carlin
> Assignee: Steve Carlin
> Priority: Major
>
> If a query fails in Calcite, we need the ability to fallback to the original
> planner.
> We need a query option for the fallback algorithm because there are at least
> 3 different ways we need to fallback
> 1) nonquery exceptions only. Calcite currently only supports queries (no
> DDL, DML, or other non-select statements). Running with this option will
> throw an exception for every query that Calcite does not support
> 2) Unsupported and nonquery exceptions: Similar to 1), but if there is a
> failure that we know explicitly fails in Calcite, an Unsupported Exception is
> thrown and we fallback to the original planner. This option is useful on data
> load because of some of the data loading uses COMPUTE STATS and under the
> covers, it runs stats on complex query columns which we do not want to fail.
> 1) All exceptions: Any exception from the Calcite planner will result in a
> retry with the original planner. This is useful in production scenarios
> where we don't want a Calcite bug to be the cause of a failed query. Normal
> jenkins test runs that run with the Calcite planner will most likely use this
> option.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
