You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@arrow.apache.org by "Wes McKinney (JIRA)" <ji...@apache.org> on 2016/09/05 20:00:23 UTC
[jira] [Commented] (ARROW-278) [Format] Struct type name
consistency in implementations and metadata
[ https://issues.apache.org/jira/browse/ARROW-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15465691#comment-15465691 ]
Wes McKinney commented on ARROW-278:
------------------------------------
See 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
>
> 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)