[jira] [Comment Edited] (DRILL-5378) Put more information into SchemaChangeException when HashJoin hit SchemaChangeException

["Jinfeng Ni (JIRA)" <ji...@apache.org>]

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

Jinfeng Ni edited comment on DRILL-5378 at 3/24/17 2:54 PM:
------------------------------------------------------------

Include HashAgg and sort operator in the proposed change as well, since those two operators does not support schema change.

Prior error message :
{code}
UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changes. 
{code}

New proposed error message in SchemaChangeException : 

{code}
UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changes. 
Prior schema : 
BatchSchema [fields=[year(VARCHAR:OPTIONAL)], selectionVector=NONE]
New schema : 
BatchSchema [fields=[year(VARCHAR:REQUIRED)], selectionVector=NONE]
{code}


was (Author: jni):
Include HashAgg and sort operator in the proposed change as well, since those two operators does not support schema change as well.

Prior error message :
{code}
UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changesSchema changed. 
{code}

New proposed error message in SchemaChangeException : 

{code}
UNSUPPORTED_OPERATION ERROR: Hash aggregate does not support schema changesSchema changed. 
Prior schema : 
BatchSchema [fields=[year(VARCHAR:OPTIONAL)], selectionVector=NONE]
New schema : 
BatchSchema [fields=[year(VARCHAR:REQUIRED)], selectionVector=NONE]
{code}

> 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)