drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4664) ScanBatch.isNewSchema() returns wrong result for map datatype
Date Thu, 14 Jul 2016 22:37:20 GMT

    [ https://issues.apache.org/jira/browse/DRILL-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15378518#comment-15378518
] 

ASF GitHub Bot commented on DRILL-4664:
---------------------------------------

Github user hnfgns commented on the issue:

    https://github.com/apache/drill/pull/516
  
    looks good to me +1 
    
    @parthchandra can we run regression and merge?


> ScanBatch.isNewSchema() returns wrong result for map datatype
> -------------------------------------------------------------
>
>                 Key: DRILL-4664
>                 URL: https://issues.apache.org/jira/browse/DRILL-4664
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - Flow
>    Affects Versions: 1.6.0
>            Reporter: Vitalii Diravka
>            Priority: Minor
>
> isNewSchema() method checks if top-level schema or any of the deeper map schemas has
changed. The last one doesn't work properly with count function.
> "deeperSchemaChanged" equals true even when two map strings have the same children fields.
> Discovered while trying to fix [DRILL-2385|DRILL-2385].
> Dataset test.json for reproducing (MAP<REQUIRED> datatype object):
> {code}{"oooi":{"oa":{"oab":{"oabc":1}}}}{code}
> Example of query:
> {code}select count(t.oooi) from dfs.tmp.`test.json` t{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message