drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5378) Put more information into SchemaChangeException when HashJoin hit SchemaChangeException
Date Tue, 28 Mar 2017 01:06:42 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944339#comment-15944339

ASF GitHub Bot commented on DRILL-5378:

Github user jinfengni commented on the issue:

    Agreed with @paul-rogers 's comment regarding overuse SchemaChangeException in the code.
I actually planned to open a jira, if no one has been opened yet. We currently use SchemaChangeException
in many situations, including real schema change or operational error for "something is wrong"

> 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

View raw message