[
https://issues.apache.org/jira/browse/DRILL-5378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15944216#comment-15944216
]
ASF GitHub Bot commented on DRILL-5378:
---------------------------------------
GitHub user jinfengni opened a pull request:
https://github.com/apache/drill/pull/801
DRILL-5378: Put more information for schema change exception in hash …
…join, hash agg and sort operator.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jinfengni/incubator-drill DRILL-5378
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/801.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #801
----
commit e29909a08146c5c766590c07015b5ba9137a8dee
Author: Jinfeng Ni <[email protected]>
Date: 2017-03-22T22:28:22Z
DRILL-5378: Put more information for schema change exception in hash join,
hash agg and sort operator.
----
> 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)
