You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Benno Evers (JIRA)" <ji...@apache.org> on 2019/04/03 16:48:00 UTC
[jira] [Commented] (MESOS-7974) Accept "application/recordio" type
is rejected for master operator API SUBSCRIBE call
[ https://issues.apache.org/jira/browse/MESOS-7974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16808914#comment-16808914 ]
Benno Evers commented on MESOS-7974:
------------------------------------
Re-targeted to 1.9.0.
> Accept "application/recordio" type is rejected for master operator API SUBSCRIBE call
> -------------------------------------------------------------------------------------
>
> Key: MESOS-7974
> URL: https://issues.apache.org/jira/browse/MESOS-7974
> Project: Mesos
> Issue Type: Bug
> Affects Versions: 1.2.1
> Reporter: James DeFelice
> Assignee: Joseph Wu
> Priority: Major
> Labels: mesosphere
>
> The agent operator API supports for "application/recordio" for things like attach-container-output, which streams objects back to the caller. I expected the master operator API SUBSCRIBE call to work the same way, w/ Accept/Content-Type headers for "recordio" and Message-Accept/Message-Content-Type headers for json (or protobuf). This was not the case.
> Looking again at the master operator API documentation, SUBSCRIBE docs illustrate usage Accept and Content-Type headers for the "application/json" type. Not a "recordio" type. So my experience, as per the docs, seems expected. However, this is counter-intuitive since the whole point of adding the new Message-prefixed headers was to help callers consistently request (and differentiate) streaming responses from non-streaming responses in the v1 API.
> Please fix the master operator API implementation to also support the Message-prefixed headers w/ Accept/Content-Type set to "recordio".
> Observed on ubuntu w/ mesos package version 1.2.1-2.0.1
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)