[jira] [Comment Edited] (MESOS-3566) Add a section to the Scheduler HTTP API docs around RecordIO specification

["Anand Mazumdar (JIRA)" <ji...@apache.org>]

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

Anand Mazumdar edited comment on MESOS-3566 at 10/16/15 1:54 PM:
-----------------------------------------------------------------

Thanks, updated description to reflect this now. For now , till we do that, I edited my earlier comment on MESOS-3562 to reflect the reasoning.

https://issues.apache.org/jira/browse/MESOS-3562?focusedCommentId=14939194&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14939194


was (Author: anandmazumdar):
Thanks, updated description to reflect this now.

> Add a section to the Scheduler HTTP API docs around RecordIO specification
> --------------------------------------------------------------------------
>
>                 Key: MESOS-3566
>                 URL: https://issues.apache.org/jira/browse/MESOS-3566
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Anand Mazumdar
>              Labels: mesosphere
>
> Since the {{RecordIO}} format is not that widely used, searching for it online does not offer much help. 
> - It would be good if we can add to the docs, a small section on its specification for framework developers. 
> - Also, add details on why {{RecordIO}} format is being used and why just using vanilla {{ChunkedEncoding}} and encode one event per chunk won't suffice.
> - Add info about the rationale behind using the {{RecordIO}} format and not just relying on encoding an event per chunk.
> - Bonus points, if we can have a simple code snippet in C++/Java on reading a {{RecordIO}} response to help developers.



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