You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@arrow.apache.org by "Rok Mihevc (Jira)" <ji...@apache.org> on 2023/01/11 07:08:04 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=17657312#comment-17657312 ]
Rok Mihevc commented on ARROW-278:
----------------------------------
This issue has been migrated to [issue #15638|https://github.com/apache/arrow/issues/15638] on GitHub. Please see the [migration documentation|https://github.com/apache/arrow/issues/14542] for further details.
> [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
> Priority: Major
> Fix For: 0.1.0
>
>
> 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
(v8.20.10#820010)