You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Jinfeng Ni (JIRA)" <ji...@apache.org> on 2017/03/24 01:23:41 UTC
[jira] [Created] (DRILL-5378) Put more information into
SchemaChangeException when HashJoin hit SchemaChangeException
Jinfeng Ni created DRILL-5378:
---------------------------------
Summary: Put more information into SchemaChangeException when HashJoin hit SchemaChangeException
Key: DRILL-5378
URL: https://issues.apache.org/jira/browse/DRILL-5378
Project: Apache Drill
Issue Type: Bug
Components: Execution - Relational Operators
Reporter: Jinfeng Ni
Assignee: Jinfeng Ni
Priority: Minor
HashJoin currently does not allow schema change in either build side or probe side. When HashJoin hit SchemaChangeException in the middle of execution, Drill reports a brief error message about SchemaChangeException, without providing any information what schemas are in the incoming batches. That makes hard to analyze the error, and understand what's going on.
It probably makes sense to put the two differing schemas in the error message, so that user could get better idea about the schema change.
Before Drill can provide support for schema change in HashJoin, the detailed error message would help user debug error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)