[jira] [Commented] (DRILL-4754) Missing values are not missing
[ https://issues.apache.org/jira/browse/DRILL-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350440#comment-15350440 ] Ted Dunning commented on DRILL-4754: This other bug (from 18 months ago with no apparent progress) notes the conflation of empty and missing, but doesn't directly address it. > Missing values are not missing > -- > > Key: DRILL-4754 > URL: https://issues.apache.org/jira/browse/DRILL-4754 > Project: Apache Drill > Issue Type: Bug >Reporter: Ted Dunning > > If I have a query which reads from a JSON file where a field is a list or is > missing, then the records where the field should missing will instead have a > value for that field that is an empty list: > {code} > 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; > +++--+ > | *a* | *b*| *c* | > | 3 | [3,2] | xyz | > | 7 | [] | wxy | > | 7 | [] | null | > +++--+ > 2 rows selected (1.279 seconds) > {code} > where the file in question contains these three records: > {code} > {'a':3, 'b':[3,2], 'c':'xyz'} > {'a':7, 'c':'wxy'} > {"a":7, "b":[]} > {code} > The problem is in the second record of the result. I would have expected b to > have had the value NULL. > I am using drill-1.6.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-4754) Missing values are not missing
[ https://issues.apache.org/jira/browse/DRILL-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350430#comment-15350430 ] Ted Dunning commented on DRILL-4754: Hmm... I can't find any such JIRA's just off hand. I see DRILL-3831, but that seems to be a very different matter. I will look further. > Missing values are not missing > -- > > Key: DRILL-4754 > URL: https://issues.apache.org/jira/browse/DRILL-4754 > Project: Apache Drill > Issue Type: Bug >Reporter: Ted Dunning > > If I have a query which reads from a JSON file where a field is a list or is > missing, then the records where the field should missing will instead have a > value for that field that is an empty list: > {code} > 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; > +++--+ > | *a* | *b*| *c* | > | 3 | [3,2] | xyz | > | 7 | [] | wxy | > | 7 | [] | null | > +++--+ > 2 rows selected (1.279 seconds) > {code} > where the file in question contains these three records: > {code} > {'a':3, 'b':[3,2], 'c':'xyz'} > {'a':7, 'c':'wxy'} > {"a":7, "b":[]} > {code} > The problem is in the second record of the result. I would have expected b to > have had the value NULL. > I am using drill-1.6.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (DRILL-4754) Missing values are not missing
[ https://issues.apache.org/jira/browse/DRILL-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15350394#comment-15350394 ] Jacques Nadeau commented on DRILL-4754: --- This is a current known limitation of Drill 1.6/current Drill master. We can't distinguish between empty list and null. (The vectors don't currently allow it.) Same goes for treating empty map and null map the same. I believe there are already some JIRAs outstanding that are specifically focused on this issue. (e.g. support nullable maps and nullable lists) > Missing values are not missing > -- > > Key: DRILL-4754 > URL: https://issues.apache.org/jira/browse/DRILL-4754 > Project: Apache Drill > Issue Type: Bug >Reporter: Ted Dunning > > If I have a query which reads from a JSON file where a field is a list or is > missing, then the records where the field should missing will instead have a > value for that field that is an empty list: > {code} > 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; > +++--+ > | *a* | *b*| *c* | > | 3 | [3,2] | xyz | > | 7 | [] | wxy | > | 7 | [] | null | > +++--+ > 2 rows selected (1.279 seconds) > {code} > where the file in question contains these three records: > {code} > {'a':3, 'b':[3,2], 'c':'xyz'} > {'a':7, 'c':'wxy'} > {"a":7, "b":[]} > {code} > The problem is in the second record of the result. I would have expected b to > have had the value NULL. > I am using drill-1.6.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (DRILL-4754) Missing values are not missing
[ https://issues.apache.org/jira/browse/DRILL-4754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Dunning updated DRILL-4754: --- Description: If I have a query which reads from a JSON file where a field is a list or is missing, then the records where the field should missing will instead have a value for that field that is an empty list: {{ 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; +++--+ | *a* | *b*| *c* | | 3 | [3,2] | xyz | | 7 | [] | wxy | | 7 | [] | null | +++--+ 2 rows selected (1.279 seconds) }} where the file in question contains these two records: {{ {'a':3, 'b':[3,2], 'c':'xyz'} {'a':7, 'c':'wxy'} {"a":7, "b":[]} }} The problem is in the second record of the result. I would have expected b to have had the value NULL. I am using drill-1.6.0. was: If I have a query which reads from a JSON file where a field is a list or is missing, then the records where the field should missing will instead have a value for that field that is an empty list: {{ 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; +++--+ | *a* | b| c | | 3 | [3,2] | xyz | | 7 | [] | wxy | | 7 | [] | null | +++--+ 2 rows selected (1.279 seconds) }} where the file in question contains these two records: {{ {'a':3, 'b':[3,2], 'c':'xyz'} {'a':7, 'c':'wxy'} {"a":7, "b":[]} }} The problem is in the second record of the result. I would have expected b to have had the value NULL. I am using drill-1.6.0. > Missing values are not missing > -- > > Key: DRILL-4754 > URL: https://issues.apache.org/jira/browse/DRILL-4754 > Project: Apache Drill > Issue Type: Bug >Reporter: Ted Dunning > > If I have a query which reads from a JSON file where a field is a list or is > missing, then the records where the field should missing will instead have a > value for that field that is an empty list: > {{ > 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; > +++--+ > | *a* | *b*| *c* | > | 3 | [3,2] | xyz | > | 7 | [] | wxy | > | 7 | [] | null | > +++--+ > 2 rows selected (1.279 seconds) > }} > where the file in question contains these two records: > {{ > {'a':3, 'b':[3,2], 'c':'xyz'} > {'a':7, 'c':'wxy'} > {"a":7, "b":[]} > }} > The problem is in the second record of the result. I would have expected b to > have had the value NULL. > I am using drill-1.6.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (DRILL-4754) Missing values are not missing
Ted Dunning created DRILL-4754: -- Summary: Missing values are not missing Key: DRILL-4754 URL: https://issues.apache.org/jira/browse/DRILL-4754 Project: Apache Drill Issue Type: Bug Reporter: Ted Dunning If I have a query which reads from a JSON file where a field is a list or is missing, then the records where the field should missing will instead have a value for that field that is an empty list: 0: jdbc:drill:> select * from maprfs.ted.`bug.json`; +++--+ | a | b| c | +++--+ | 3 | [3,2] | xyz | | 7 | [] | wxy | +++--+ 2 rows selected (1.279 seconds) where the file in question contains these two records: {'a':3, 'b':[3,2], 'c':'xyz'} {'a':7, 'c':'wxy'} The problem is in the second record of the result. I would have expected b to have had the value NULL. I am using drill-1.6.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)