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

ASF GitHub Bot commented on DRILL-7576:
---------------------------------------

ihuzenko commented on pull request #1975: DRILL-7576: Fail fast for operator 
errors
URL: https://github.com/apache/drill/pull/1975#discussion_r376945843
 
 

 ##########
 File path: 
exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/aggregate/HashAggBatch.java
 ##########
 @@ -340,16 +340,12 @@ public IterOutcome innerNext() {
       }
 
     case UPDATE_AGGREGATOR:
-      context.getExecutorState().fail(UserException.unsupportedError()
+      throw UserException.unsupportedError()
           .message(SchemaChangeException.schemaChanged(
               "Hash aggregate does not support schema change",
               incomingSchema,
               incoming.getSchema()).getMessage())
-          .build(logger));
-      close();
-      killIncoming(false);
-      firstBatch = false;
-      return IterOutcome.STOP;
+          .build(logger);
 
 Review comment:
   could you please explain why ```close()``` and ```killIncoming(false)``` 
invocations were removed for the case?
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


> Fail fast in operators
> ----------------------
>
>                 Key: DRILL-7576
>                 URL: https://issues.apache.org/jira/browse/DRILL-7576
>             Project: Apache Drill
>          Issue Type: Improvement
>    Affects Versions: 1.17.0
>            Reporter: Paul Rogers
>            Assignee: Paul Rogers
>            Priority: Major
>             Fix For: 1.18.0
>
>
> Continues to the work to clean up operators to "fail fast" by throwing an 
> exception instead of using the more involved STOP status.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to