[jira] [Commented] (ARROW-6818) [Doc] Format docs confusing

["Martin Blostein (Jira)" <ji...@apache.org>]

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

Martin Blostein commented on ARROW-6818:
----------------------------------------

I think this issue has mostly been resolved:
1. Map isn't mentioned anywhere in the Format doc anymore.

2. The document says explicitly: "We do not go into detail about the logical types definitions in this document as we consider `Schema.fbs`_ to be authoritative." I don't this is clear, and avoids things getting out of sync. So I don't think it is confusing.

3. "Relative type" doesn't appear anywhere in the doc anymore. 

4. There is still a reference to the Apache Drill design docs and I agree it is not clear why. I will open a PR to remove this link.

> [Doc] Format docs confusing
> ---------------------------
>
>                 Key: ARROW-6818
>                 URL: https://issues.apache.org/jira/browse/ARROW-6818
>             Project: Apache Arrow
>          Issue Type: Bug
>          Components: Documentation, Format
>            Reporter: Antoine Pitrou
>            Assignee: Micah Kornfield
>            Priority: Major
>
> I find there are several issues in the format docs.
> 1) there is a claimed distinction between "logical types" and "physical types", but the "physical types" actually lists logical types such as Map
> 2) the "logical types" document doesn't actually list logical types, it just sends to the flatbuffers file. One shouldn't have to read a flatbuffers file to understand the Arrow format.
> 3) some terminology seems unusual, such as "relative type"
> 4) why is there a link to the Apache Drill docs?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)