You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Arina Ielchiieva (JIRA)" <ji...@apache.org> on 2016/07/16 14:47:20 UTC
[jira] [Resolved] (DRILL-4664) ScanBatch.isNewSchema() returns
wrong result for map datatype
[ https://issues.apache.org/jira/browse/DRILL-4664?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arina Ielchiieva resolved DRILL-4664.
-------------------------------------
Resolution: Fixed
Fix Version/s: 1.8.0
Fixed with commid id 05c42eae79ce3e309028b3824f9449b98e329f29.
> 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
> Assignee: Vitalii Diravka
> Priority: Minor
> Fix For: 1.8.0
>
>
> 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)