drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5546) Schema change problems caused by empty batch
Date Tue, 29 Aug 2017 22:08:00 GMT

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

ASF GitHub Bot commented on DRILL-5546:

Github user jinfengni commented on a diff in the pull request:

    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/project/ProjectRecordBatch.java
    @@ -768,4 +765,73 @@ else if (exprHasPrefix && refHasPrefix) {
    +  /**
    +   * handle FAST NONE specially when Project for query output. This happens when input
returns a
    --- End diff --
    I change to "handleNullInput" from "handleFastNone". 
    The concept of "NullInput" captures the scenarios where input does not produce any batch,
and returning NONE directly.  The concept of "empty result set" could mean the case where
we have 0 row, but still we could have a batch. I think "empty result set" is not precisely
what we want to cover here. 

> Schema change problems caused by empty batch
> --------------------------------------------
>                 Key: DRILL-5546
>                 URL: https://issues.apache.org/jira/browse/DRILL-5546
>             Project: Apache Drill
>          Issue Type: Bug
>            Reporter: Jinfeng Ni
>            Assignee: Jinfeng Ni
> There have been a few JIRAs opened related to schema change failure caused by empty batch.
This JIRA is opened as an umbrella for all those related JIRAS ( such as DRILL-4686, DRILL-4734,
DRILL4476, DRILL-4255, etc).

This message was sent by Atlassian JIRA

View raw message