You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Sudheesh Katkam (JIRA)" <ji...@apache.org> on 2015/05/07 20:56:02 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=14531748#comment-14531748 ] 

Sudheesh Katkam edited comment on DRILL-2476 at 5/7/15 6:55 PM:
----------------------------------------------------------------

-I will post the patch to review board as soon as DRILL-2895 (part of DRILL-2757) is merged.-
Review board: https://reviews.apache.org/r/33949/


was (Author: sudheeshkatkam):
I will post the patch to review board as soon as DRILL-2895 (part of DRILL-2757) is merged.

> 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: 1.0.0
>
>         Attachments: DRILL-2476.1.patch.txt
>
>
> 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)