Mailing-List: contact dev-help@arrow.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@arrow.apache.org
Date: Wed, 7 Sep 2016 21:16:20 +0000 (UTC)
From: "Julien Le Dem (JIRA)" <jira@apache.org>
To: dev@arrow.apache.org
Message-ID: <JIRA.13000500.1472241477000.512498.1473282980764@Atlassian.JIRA>
In-Reply-To: <JIRA.13000500.1472241477000@Atlassian.JIRA>
References: <JIRA.13000500.1472241477000@Atlassian.JIRA> <JIRA.13000500.1472241477363@arcas>
Subject: [jira] [Resolved] (ARROW-278) [Format] Struct type name consistency
 in implementations and metadata
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Sep 2016 21:16:22 -0000


     [ https://issues.apache.org/jira/browse/ARROW-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julien Le Dem resolved ARROW-278.
---------------------------------
    Resolution: Fixed

Issue resolved by pull request 130
[https://github.com/apache/arrow/pull/130]

> [Format] Struct type name consistency in implementations and metadata
> ---------------------------------------------------------------------
>
>                 Key: ARROW-278
>                 URL: https://issues.apache.org/jira/browse/ARROW-278
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Format
>            Reporter: Wes McKinney
>            Assignee: Wes McKinney
>
> As discussed in https://github.com/apache/arrow/pull/121 for ARROW-262, the {{Struct}} name is reserved in Flatbuffers, so we temporarily used the `{{Tuple}}` name. We should either use a tweaked name like {{Struct_}} that does not cause conflicts or choose a name for the Struct concept (e.g. {{Tuple}}) and use that consistently in format documents and implementation.
> The least disruptive solution is to use the {{Struct_}} name in the Flatbuffers IDL.


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