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-4733) max(dir0) reading more columns than necessary
Date Tue, 21 Jun 2016 20:20:57 GMT

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

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

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

    https://github.com/apache/drill/pull/531#discussion_r67943855
  
    --- Diff: exec/java-exec/src/test/java/org/apache/drill/exec/store/TestImplicitFileColumns.java
---
    @@ -110,4 +111,20 @@ public void testImplicitColumnsForParquet() throws Exception {
             .go();
       }
     
    +  @Test // DRILL-4733
    +  public void testMultilevelParquetWithSchemaChange() throws Exception {
    +    try {
    +      test("alter session set `planner.enable_decimal_data_type` = true");
    +      testBuilder()
    +          .sqlQuery(String.format("select max(dir0) as max_dir from dfs_test.`%s/src/test/resources/multilevel/parquetWithSchemaChange`",
    +              TestTools.getWorkingPath()))
    +          .unOrdered()
    +          .baselineColumns("max_dir")
    +          .baselineValues("voter50.parquet")
    --- End diff --
    
    Why do you put baselineValue in a parquet, in stead of putting it in the testcase directly?
Tthe query seems to return one single value. 


> max(dir0) reading more columns than necessary
> ---------------------------------------------
>
>                 Key: DRILL-4733
>                 URL: https://issues.apache.org/jira/browse/DRILL-4733
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Query Planning & Optimization, Storage - Parquet
>    Affects Versions: 1.7.0
>            Reporter: Rahul Challapalli
>            Assignee: Arina Ielchiieva
>            Priority: Critical
>             Fix For: 1.7.0
>
>         Attachments: bug.tgz
>
>
> The below query started to fail from this commit : 3209886a8548eea4a2f74c059542672f8665b8d2
> {code}
> select max(dir0) from dfs.`/drill/testdata/bug/2016`;
> Error: UNSUPPORTED_OPERATION ERROR: Streaming aggregate does not support schema changes
> Fragment 0:0
> [Error Id: b0060205-e9a6-428a-9803-7b4312b2c6f4 on qa-node190.qa.lab:31010] (state=,code=0)
> {code}
> The sub-folders contains files which do have schema change for one column "contributions"
(int32 vs double). However prior to this commit we did not fail in the scenario. Log files
and test data are attached



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

Mime
View raw message