-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 1.12.0
-
Component/s: None
-
Labels:None
There have been a few JIRAs opened related to schema change failure caused by empty batch. This JIRA is opened as an umbrella for all those related JIRAS ( such as DRILL-4686, DRILL-4734, DRILL4476, DRILL-4255, etc).
- causes
-
DRILL-6774 Wrong data types of empty batches schema for queries with aliases
-
- Open
-
-
DRILL-6773 The renamed schema with aliases is not shown for queries on empty directories
-
- Resolved
-
- incorporates
-
DRILL-2775 message error not clear when doing a select or ctas on empty folder
-
- Resolved
-
- is related to
-
DRILL-4185 UNION ALL involving empty directory on any side of union all results in Failed query
-
- Resolved
-
- relates to
-
DRILL-4255 SELECT DISTINCT query over JSON data returns UNSUPPORTED OPERATION
-
- Resolved
-
-
DRILL-4476 Enhance Union-All operator for dealing with empty left input or empty both inputs
-
- Resolved
-
-
DRILL-4686 Aggregation query over HBase table results in IllegalStateException: Failure while reading vector
-
- Resolved
-
-
DRILL-4734 Query against HBase table on a 5 node cluster fails with SchemaChangeException
-
- Resolved
-
-
DRILL-5185 Union all not passing type info when the output contains 0 rows
-
- Resolved
-
-
DRILL-5327 Hash aggregate can return empty batch which can cause schema change exception
-
- Resolved
-
-
DRILL-5464 Fix JSON reader when it deals with empty file
-
- Resolved
-
-
DRILL-5480 Empty batch returning from HBase may cause SchemaChangeException even when data does not have different schema
-
- Resolved
-
- supercedes
-
DRILL-2618 BasicFormatMatcher calls getFirstPath(...) without checking # of paths is not zero
-
- Closed
-
- links to