[
https://issues.apache.org/jira/browse/DRILL-7092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16793482#comment-16793482
]
Arina Ielchiieva edited comment on DRILL-7092 at 3/15/19 9:26 AM:
------------------------------------------------------------------
Merged with commit id fbbfbefaadd54d819cfd8e10ce274f4f086d1fb8.
was (Author: arina):
merged with commit id fbbfbefaadd54d819cfd8e10ce274f4f086d1fb8.
> Rename map to struct in schema definition
> -----------------------------------------
>
> Key: DRILL-7092
> URL: https://issues.apache.org/jira/browse/DRILL-7092
> Project: Apache Drill
> Issue Type: Sub-task
> Reporter: Arina Ielchiieva
> Assignee: Arina Ielchiieva
> Priority: Major
> Labels: ready-to-commit
> Fix For: 1.16.0
>
>
> Drill maps concept is more close to Struct concept. Good write up by Paul
> about this:
> https://github.com/paul-rogers/drill/wiki/Drill-Maps. Internally such objects
> are represented by MapVector which in future will be renamed to StructVector
> (similar was done in Arrow project). Drill also does not support true maps,
> which in future will be also implemented with proper naming (MapVector).
> Nevertheless, internal map / struct presentation does not affect users plus
> before schema provisioning they did not deal with this concept at all.
> Initially map complex type in Schema Provisioning schema was represented with
> map keyword followed by angle brackets: col1 map<m1 int, m2 int>. Given
> second thought to map notion, looks like it's better to use struct in schema
> definition and internally convert it to map metadata (again which eventually
> will be renamed to struct). Such approach would ease map to struct renaming
> (since it will be done internally) and users will be using struct naming as
> before. Once Drill will implement true map, schema provisioning will allow
> map type for schema.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
