You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/09/06 13:15:00 UTC

[jira] [Commented] (DRILL-7369) Schema for MaprDB tables is not used for the case when several field are queried

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

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

vvysotskyi commented on pull request #1852: DRILL-7369: Schema for MaprDB tables is not used for the case when several field are queried
URL: https://github.com/apache/drill/pull/1852
 
 
   For problem description please refer to [DRILL-7369](https://issues.apache.org/jira/browse/DRILL-7369).
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Schema for MaprDB tables is not used for the case when several field are queried
> --------------------------------------------------------------------------------
>
>                 Key: DRILL-7369
>                 URL: https://issues.apache.org/jira/browse/DRILL-7369
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Storage - MapRDB
>    Affects Versions: 1.17.0
>            Reporter: Volodymyr Vysotskyi
>            Assignee: Volodymyr Vysotskyi
>            Priority: Major
>             Fix For: 1.17.0
>
>
> In DRILL-7313 was allowed using Hive schema for MaprDB native reader when field was empty. But current code creates additional fields from schema only for the case when the incoming map is empty.
> The aim of this Jira is to allow using provided schema for the case when some fields already present.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)