Affects Version/s: None
Fix Version/s: 0.4.0
Every single batch coming off the wire is treated as having a new schema, even if it isn't.
The problem is that oldVectors is Map<MaterializedField,ValueVector>, but we are calling oldFields.remove(fieldDef), where fieldDef is a type FieldDef. Java doesn't do a check in this instance, and this call simply returns null.
This bug actually masked another problem. If it did not return null, the returned vector is added to container, but it should be added to newVectors. We also don't load the vector with data from the incoming ByteBuf.
|Workflow||no-reopen-closed, patch-avail, testing [ 12860526 ]||Drill workflow [ 12935734 ]|
|Fix Version/s||0.4.0 [ 12324963 ]|
|Workflow||no-reopen-closed, patch-avail [ 12827724 ]||no-reopen-closed, patch-avail, testing [ 12860526 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Assignee||Steven Phillips [ sphillips ]|
|Resolution||Fixed [ 1 ]|
|Field||Original Value||New Value|
|Summary||RecordBatchLoader.load always creates new schem||RecordBatchLoader.load always creates new schema|