Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
1.1.0
-
None
Description
The source data contains -
20K rows with the following -
{"some":"yes","others":{"other":"true","all":"false","sometimes":"yes"}}
200 rows with the following -
{"some":"yes","others":{"other":"true","all":"false","sometimes":"yes","additional":"last
entries only"}}
Creating a table and reading it back returns incorrect data -
CREATE TABLE testparquet as select * from `test.json`;
SELECT * from testparquet;
Yields
yes | {"other":"true","all":"false","sometimes":"yes"} |
yes | {"other":"true","all":"false","sometimes":"yes"} |
yes | {"other":"true","all":"false","sometimes":"yes"} |
yes | {"other":"true","all":"false","sometimes":"yes"} |
The "additional" field is missing in all records
Parquet metadata for the created file does not have the 'additional' field
Attachments
Issue Links
- is related to
-
DRILL-3577 Counting nested fields on CTAS-created-parquet file/s reports inaccurate results
- Closed
- relates to
-
DRILL-3476 Filter on nested element gives wrong results
- Closed