[DRILL-2476] Handle IterOutcome.STOP in buildSchema()

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.7.0
• Fix Version/s: 1.0.0
• Component/s: Execution - Relational Operators
• Assignee: Steven Phillips
• Reporter: Sudheesh Katkam
• Created: 16/Mar/15 18:31
• Updated: 12/May/15 08:33
• Resolved: 12/May/15 08:33

Description

There are some RecordBatch implementations like HashAggBatch that override the buildSchema() function. The overriding functions do not handle IterOutcome.STOP. This causes the FragmentContext to receive two failures in some cases (linked JIRAs).

Issue Links

• contains: DRILL-2206 Error message must be updated when querying a JSON file with arrays in first level
• contains: DRILL-1891 Error message does not get propagated correctly when reading from JSON file
• is part of: DRILL-2895 AbstractRecordBatch.buildSchema() should properly handle OUT_OF_MEMORY outcome
• is related to: DRILL-2475 Handle IterOutcome.NONE correctly in operators
• is related to: DRILL-2524 When json records are separated by a 'COMMA'(which drill does not support), we should throw a proper error
• is related to: DRILL-2666 Query against json profile with large number of fragments fails