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/05/06 19:00:00 UTC
[jira] [Commented] (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=14530913#comment-14530913 ]
Deneche A. Hakim commented on DRILL-2476:
-----------------------------------------
as part of DRILL-2757 I fixed some the operators to handle STOP in buildSchema() but not all of them. The following operators still don't handle STOP in buildSchema():
- NestedLoopJoinBatch
- MergingRecordBatch
- MergeJoinBatch
- HashJoinBatch
> 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
>
>
> 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)