[DRILL-2022] Parquet engine falls back to "new" Parquet reader unnecessarily

• Type: Improvement
• Status: Reviewable
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 0.8.0
• Fix Version/s: Future
• Component/s: Storage - Parquet
• Assignee: Jason Altekruse
• Reporter: Adam Gilmore
• Created: 16/Jan/15 09:04
• Updated: 24/Jun/16 21:50

Description

The Parquet engine falls back to the "new" Parquet reader whenever a Parquet file that is "complex" (i.e. not purely primitive types) is found.

The engine should still use the faster reader when all the projected columns are primitive types and only fall back to the other reader when columns containing complex types are selected.