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-6223) Drill fails on Schema changes
Date Fri, 30 Mar 2018 03:10:00 GMT

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

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

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

    https://github.com/apache/drill/pull/1170#discussion_r178222960
  
    --- Diff: exec/java-exec/src/main/java/org/apache/drill/exec/physical/impl/limit/LimitRecordBatch.java
---
    @@ -60,13 +60,7 @@ public LimitRecordBatch(Limit popConfig, FragmentContext context, RecordBatch
in
       protected boolean setupNewSchema() throws SchemaChangeException {
         container.zeroVectors();
         transfers.clear();
    -
    -
    -    for(final VectorWrapper<?> v : incoming) {
    -      final TransferPair pair = v.getValueVector().makeTransferPair(
    -          container.addOrGet(v.getField(), callBack));
    -      transfers.add(pair);
    -    }
    +    container.onSchemaChange(incoming, callBack, transfers);
    --- End diff --
    
    `onSchemaChange()` may perhaps be the wrong name. It is why this functionality is called
in this case. But, the actual functionality is closer to `setupTransfers()` (assuming the
removed code was simply moved into the container class...)


> Drill fails on Schema changes 
> ------------------------------
>
>                 Key: DRILL-6223
>                 URL: https://issues.apache.org/jira/browse/DRILL-6223
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Relational Operators
>    Affects Versions: 1.10.0, 1.12.0
>            Reporter: salim achouche
>            Assignee: salim achouche
>            Priority: Major
>             Fix For: 1.14.0
>
>
> Drill Query Failing when selecting all columns from a Complex Nested Data File (Parquet)
Set). There are differences in Schema among the files:
>  * The Parquet files exhibit differences both at the first level and within nested data
types
>  * A select * will not cause an exception but using a limit clause will
>  * Note also this issue seems to happen only when multiple Drillbit minor fragments are
involved (concurrency higher than one)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message