[ https://issues.apache.org/jira/browse/DRILL-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16403951#comment-16403951 ]
Parth Chandra commented on DRILL-6223: -------------------------------------- Once again, without having looked at the actual PR: If you have schema changes occurring in the source files and the Parquet metadata overwrites the types for a column whose type has mutated, then everything else downstream is irrelevant. So please take a look at it. On a more fundamental note, +1 to [~paul-rogers]'s comment on formalizing the schema change specification before fixing issues related to schema change. > 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)