You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Deneche A. Hakim (JIRA)" <ji...@apache.org> on 2015/03/17 01:49:38 UTC
[jira] [Comment Edited] (DRILL-2476) Handle IterOutcome.STOP in
buildSchema()
[ https://issues.apache.org/jira/browse/DRILL-2476?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364323#comment-14364323 ]
Deneche A. Hakim edited comment on DRILL-2476 at 3/17/15 12:48 AM:
-------------------------------------------------------------------
All operators that extend {{AbstractRecordBatch}} won't handle correctly {{IterOutcome.STOP}} in {{buildSchema()}}
was (Author: adeneche):
All operators that extend AbstractRecordBatch won't handle correctly {{IterOutcome.STOP}} in {{buildSchema()}}
> Handle IterOutcome.STOP in buildSchema()
> ----------------------------------------
>
> Key: DRILL-2476
> URL: https://issues.apache.org/jira/browse/DRILL-2476
> Project: Apache Drill
> Issue Type: Bug
> Components: Execution - Relational Operators
> Affects Versions: 0.7.0
> Reporter: Sudheesh Katkam
> Assignee: Sudheesh Katkam
> Fix For: 0.9.0
>
>
> There are some {{RecordBatch}} implementations like {{HashAggBatch}} that override the {{buildSchema()}} function. The overriding functions do not handle {{IterOutcome.STOP}}. This causes the {{FragmentContext}} to receive two failures in some cases (linked JIRAs).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)