Details
-
Bug
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
Currently when a field has literal null values in JSON the type will be assigned as BIGINT by default for lack of better type.
```
{
"a": null
}
```
if later on a is assigned with a string value the query will fail with a schema change error,
The idea is to capture the notion of "untyped null" and implement simple type promotion from untyped null to the actual type.
Attachments
Attachments
Issue Links
- relates to
-
DRILL-3577 Counting nested fields on CTAS-created-parquet file/s reports inaccurate results
-
- Closed
-
-
DRILL-4479 JsonReader should pick a less restrictive type when creating the default column
-
- Closed
-
-
DRILL-4614 Drill must appoint one data type per one column for self-describing data while querying directories
-
- Closed
-
-
DRILL-4824 Null maps / lists and non-provided state support for JSON fields. Numeric types promotion.
-
- Open
-