[
https://issues.apache.org/jira/browse/DRILL-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16419709#comment-16419709
]
salim achouche commented on DRILL-6223:
---------------------------------------
* I concur that we need to a) ultimately formalize the schema change behavior
and b) clarify how it can be useful to the Drill users
** I have created a new Jira for this effort DRILL-6297
** This hopefully will allow us to address current bugs and even schedule
future enhancements
* Back to this Jira
** There are currently Drill users hitting schema changes issues
** Our JDBC client has logic to detect that a schema change occurred and
consequently notify the client of this event and reload the metadata
** The question now is on whether we should wait till DRILL-6297 is resolved
** Or try to address some of these bugs albeit temporarily till the associated
functionality is refined
** If you feel that we should wait, then I suggest that we disable this
functionality so that it doesn't destabilize Drill especially that the runtime
checks are disabled by default
*** The bugs that I have addressed would have corrupted the Drillbit if it
weren't for the runtime checks
> 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)
