[jira] [Updated] (MESOS-6597) Include missing Mesos Java classes for Protobuf files to support Operator HTTP V1 API
[ https://issues.apache.org/jira/browse/MESOS-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Srinivasaraghavan updated MESOS-6597: --- Summary: Include missing Mesos Java classes for Protobuf files to support Operator HTTP V1 API (was: Include additional missing Mesos Java classes from the Protobuf file to support V1 API) > Include missing Mesos Java classes for Protobuf files to support Operator > HTTP V1 API > - > > Key: MESOS-6597 > URL: https://issues.apache.org/jira/browse/MESOS-6597 > Project: Mesos > Issue Type: Bug > Components: build >Reporter: Vijay Srinivasaraghavan > > For V1 API support, the build file that generates Java protos wrapper as of > now included only executor and scheduler. > (https://github.com/apache/mesos/blob/master/src/Makefile.am#L334) > To support operator HTTP API, we also need to generate java protos for > additional proto definitions like quota, maintenance etc., These java > definition files will be used by a standard Rest client when using the > straight HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6597) Include missing Mesos Java classes for Protobuf files to support Operator HTTP V1 API
[ https://issues.apache.org/jira/browse/MESOS-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vijay Srinivasaraghavan updated MESOS-6597: --- Description: For V1 API support, the build file that generates Java protos wrapper as of now includes only executor and scheduler. (https://github.com/apache/mesos/blob/master/src/Makefile.am#L334) To support operator HTTP API, we also need to generate java protos for additional proto definitions like quota, maintenance etc., These java definition files will be used by a standard Rest client when using the straight HTTP API. was: For V1 API support, the build file that generates Java protos wrapper as of now included only executor and scheduler. (https://github.com/apache/mesos/blob/master/src/Makefile.am#L334) To support operator HTTP API, we also need to generate java protos for additional proto definitions like quota, maintenance etc., These java definition files will be used by a standard Rest client when using the straight HTTP API. > Include missing Mesos Java classes for Protobuf files to support Operator > HTTP V1 API > - > > Key: MESOS-6597 > URL: https://issues.apache.org/jira/browse/MESOS-6597 > Project: Mesos > Issue Type: Bug > Components: build >Reporter: Vijay Srinivasaraghavan > > For V1 API support, the build file that generates Java protos wrapper as of > now includes only executor and scheduler. > (https://github.com/apache/mesos/blob/master/src/Makefile.am#L334) > To support operator HTTP API, we also need to generate java protos for > additional proto definitions like quota, maintenance etc., These java > definition files will be used by a standard Rest client when using the > straight HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6597) Include missing Mesos Java classes for Protobuf files to support Operator HTTP V1 API
[ https://issues.apache.org/jira/browse/MESOS-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Anand Mazumdar updated MESOS-6597: -- Shepherd: Anand Mazumdar Target Version/s: 1.1.1, 1.2.0 Priority: Blocker (was: Major) > Include missing Mesos Java classes for Protobuf files to support Operator > HTTP V1 API > - > > Key: MESOS-6597 > URL: https://issues.apache.org/jira/browse/MESOS-6597 > Project: Mesos > Issue Type: Bug > Components: build >Reporter: Vijay Srinivasaraghavan >Assignee: Vijay Srinivasaraghavan >Priority: Blocker > > For V1 API support, the build file that generates Java protos wrapper as of > now includes only executor and scheduler. > (https://github.com/apache/mesos/blob/master/src/Makefile.am#L334) > To support operator HTTP API, we also need to generate java protos for > additional proto definitions like quota, maintenance etc., These java > definition files will be used by a standard Rest client when using the > straight HTTP API. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
