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 Mon, 21 Aug 2017 19:54:02 GMT

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

ASF GitHub Bot commented on DRILL-5546:
---------------------------------------

Github user paul-rogers commented on a diff in the pull request:

    https://github.com/apache/drill/pull/906#discussion_r134287754
  
    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/physical/config/Project.java
---
    @@ -46,14 +56,18 @@ public Project(@JsonProperty("exprs") List<NamedExpression>
exprs, @JsonProperty
         return exprs;
       }
     
    +  public boolean isOutputProj() {
    --- End diff --
    
    Maybe a comment to explain the purpose of this attribute? To quote from the PR description:
    
    > Add a new flag 'outputProj' to Project operator, to indicate if Project is for the
query's final output. Such Project is added by TopProjectVisitor, to handle fast NONE when
all the inputs to the query are empty
    and are skipped.


> 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
(v6.4.14#64029)

Mime
View raw message