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

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

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

    https://github.com/apache/drill/pull/531#discussion_r67914754
  
    --- 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");
    --- End diff --
    
    Why is decimal type relevant for this particular test ? 


> 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)

Reply via email to