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

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

Github user paul-rogers commented on the issue:

    https://github.com/apache/drill/pull/1106
  
    Note that a similar bug was recently fixed in (as I recall) the Merge 
Receiver. As part of this fix, would be good to either:
    
    1. Determine if we have more copies of this logic besides the Merge 
Receiver (previously fixed) and the client code (fixed here.)
    2. Refactor the code so that all use cases use a common set of code for 
this task.
    
    In any event, would be good to compare this code with that done in the 
Merge Receiver to ensure that we are using a common approach. See 
`exec/java-exec/src/main/java/org/apache/drill/exec/record/BatchSchema.java` in 
PR #968.
    
    The two sets of code appear similar, depending on what `isSameSchema()` 
does with a list of `MaterializedField`s. But, please take a look.


> Query fails on nested data type schema change
> ---------------------------------------------
>
>                 Key: DRILL-6129
>                 URL: https://issues.apache.org/jira/browse/DRILL-6129
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - CLI
>    Affects Versions: 1.10.0
>            Reporter: salim achouche
>            Assignee: salim achouche
>            Priority: Minor
>             Fix For: 1.13.0
>
>
> Use-Case -
>  * Assume two parquet files with similar schemas except for a nested column
>  * Schema file1
>  ** int64 field1
>  ** optional group field2
>  *** optional group field2.1 (LIST)
>  **** repeated group list
>  ***** optional group element
>  ****** optional int64 child_field
>  * Schema file2
>  ** int64 field1
>  ** optional group field2
>  *** optional group field2.1 (LIST)
>  **** repeated group list
>  ***** optional group element
>  ****** optional group child_field
>  ******* optional int64 child_field_f1
>  ******* optional int64 child_field_f1
>  * Essentially child_field changed from an int64 to a group of fields
>  
> Observed Query Failure
> select * from <file1 and file2>;
> Error: Unexpected RuntimeException: java.lang.IllegalArgumentException: The 
> field $bits$(UINT1:REQUIRED) doesn't match the provided metadata major_type {
>   minor_type: MAP
>   mode: REQUIRED
> Note that selecting one file at a time succeeds which seems to indicate the 
> issue has to do with the schema change logic. 
>  
>  



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

Reply via email to