Zoltán Borók-Nagy created IMPALA-15662:
------------------------------------------
Summary: Profile records only the exception class when the Calcite
planner falls back to the original planner
Key: IMPALA-15662
URL: https://issues.apache.org/jira/browse/IMPALA-15662
Project: IMPALA
Issue Type: Improvement
Components: Frontend
Reporter: Zoltán Borók-Nagy
When Calcite planning throws, Frontend plans the query with the original
planner (FALLBACK_PLANNER defaults to ORIGINAL) and
Frontend.addPlannerToProfile() records the failure as
firstAttemptException.getClass() (master 1a26e1f778). The profile then shows
only:
{noformat}
FirstAttemptFailureReason: class java.lang.RuntimeException
{noformat}
The message is lost. In one case it was:
{noformat}
Error while applying rule MaterializedViewJoinRule(Filter) ...
Type mismatch: the field sizes are not equal
{noformat}
Without it, a query that unexpectedly runs with the original planner gives no
clue why, and finding the cause needs FALLBACK_PLANNER=NONE or the planner
debug log. This is easy to miss in benchmarks: the plan looks normal and only
its performance differs.
*Proposal:* record the exception message (truncated) together with its class,
and consider a metric that counts fallbacks.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
