[DRILL-1459] Invalid field materialization causes vectors being created multiple times and crashes jvm in case a nested field is accessed

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 0.7.0
• Assignee: Parth Chandra
• Reporter: Hanifi Gunes
• Created: 26/Sep/14 19:47
• Updated: 09/Dec/14 17:47
• Resolved: 28/Oct/14 21:27

Description

Currently RecordBatchLoader#load relies on MaterializedField#create to materialize a SerializedField. However, MaterializedField#create method disregards child fields of SerializedField so the resultant materialized field has only the root of the given serialized field. Instead, child fields are added during vectorization.

Next time, we hit to RecordBatchLoader#load method, materialized field check fails because the previous materialized field now has children but newly materialized field does not. This misleads RecordBatchLoader#load to think that schema has changed and to create a new vector even though schema is the same.

Additionally, running a nested query on the previously created vector instance crashes the jvm.