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/04/29 17:14:06 UTC

[jira] [Commented] (DRILL-2895) AbstractRecordBatch.buildSchema() should properly handle OUT_OF_MEMORY outcome

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

Deneche A. Hakim commented on DRILL-2895:
-----------------------------------------

I will have to change BatchState anyway, so I will fix DRILL-2476 along DRILL-2895

> AbstractRecordBatch.buildSchema() should properly handle OUT_OF_MEMORY outcome
> ------------------------------------------------------------------------------
>
>                 Key: DRILL-2895
>                 URL: https://issues.apache.org/jira/browse/DRILL-2895
>             Project: Apache Drill
>          Issue Type: Sub-task
>          Components: Execution - Relational Operators
>            Reporter: Deneche A. Hakim
>            Assignee: Deneche A. Hakim
>             Fix For: 1.0.0
>
>
> currently, and in the unlikely event where we hit an out of memory exception while building the schema, operators that extend _AbstractRecordBatch_ don't handle this properly.
> Extend AbstractRecordBatch.BatchState to allow reporting OUT_OF_MEMORY back to the root.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)