You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Vijay Srinivasaraghavan <vi...@yahoo.com.INVALID> on 2016/11/15 19:38:03 UTC
Mesos V1 Operator HTTP API - Java Proto Classes
Hello,
I am writing a rest client for "operator APIs" and found that some of the protobuf java classes (like "include/mesos/v1/quota/quota.proto", "include/mesos/v1/master/master.proto") are not included in the mesos jar file. While investigating, I have found that the "Make" file does not include these proto definition files.
I have updated the Make file and added the protos that I am interested in and built a new jar file. Is there any reason why these proto definitions are not included in the original build apart from the reason that the APIs are still evolving?
RegardsVijay
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Joseph Wu <jo...@mesosphere.io>.
Added. Welcome to the contributors list :)
On Wed, Nov 16, 2016 at 9:49 AM, Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> wrote:
> I have created a JIRA and will submit a patch. Could someone please add me
> to the contributor list as I am not able to assign the JIRA to myself?
>
> https://issues.apache.org/jira/browse/MESOS-6597
>
>
>
>
> On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar <an...@apache.org>
> wrote:
>
>
> We wanted to move the project away from officially supporting anything
> other than C++ and discuss more on if we should be responsible for
> publishing to the various language specific channels. However, for the time
> being, we had decided to include the v1 protobufs in the mesos JAR itself.
> (it already contains the v1 Scheduler/Executor protos)
>
> Please file an issue as Zameer pointed out.
>
> -anand
>
> On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
>
> > I think this is a bug, I feel the jar should include all v1 protobuf
> files.
> >
> > Vijay, I encourage you to file a ticket.
> >
> > On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> > vijikarthi@yahoo.com.invalid> wrote:
> >
> >> I believe the HTTP API will use the same underlying message format
> (proto
> >> def) and hence the request/response value objects (java) needs to be
> >> auto-generated from the proto files for it to be used in Jersey based
> java
> >> rest client?
> >>
> >> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> >> janiszt@gmail.com> wrote:
> >>
> >>
> >> I suspect jar is deprecated and includes only old API used by mesoslib.
> >> The
> >> goal is to create HTTP API and stop supporting native libs (jars, so,
> >> etc).
> >> I think you shouldn't use that jar in your project.
> >>
> >> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> >> vijikarthi@yahoo.com> napisał:
> >>
> >> > Hello,
> >> >
> >> > I am writing a rest client for "operator APIs" and found that some of
> >> the
> >> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> >> > "include/mesos/v1/master/master.proto") are not included in the mesos
> >> jar
> >> > file. While investigating, I have found that the "Make" file does not
> >> > include these proto definition files.
> >> >
> >> > I have updated the Make file and added the protos that I am interested
> >> in
> >> > and built a new jar file. Is there any reason why these proto
> >> definitions
> >> > are not included in the original build apart from the reason that the
> >> APIs
> >> > are still evolving?
> >> >
> >> > Regards
> >> > Vijay
> >> >
> >>
> >> --
> >> Zameer Manji
> >>
> >
>
>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Joseph Wu <jo...@mesosphere.io>.
Added. Welcome to the contributors list :)
On Wed, Nov 16, 2016 at 9:49 AM, Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> wrote:
> I have created a JIRA and will submit a patch. Could someone please add me
> to the contributor list as I am not able to assign the JIRA to myself?
>
> https://issues.apache.org/jira/browse/MESOS-6597
>
>
>
>
> On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar <an...@apache.org>
> wrote:
>
>
> We wanted to move the project away from officially supporting anything
> other than C++ and discuss more on if we should be responsible for
> publishing to the various language specific channels. However, for the time
> being, we had decided to include the v1 protobufs in the mesos JAR itself.
> (it already contains the v1 Scheduler/Executor protos)
>
> Please file an issue as Zameer pointed out.
>
> -anand
>
> On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
>
> > I think this is a bug, I feel the jar should include all v1 protobuf
> files.
> >
> > Vijay, I encourage you to file a ticket.
> >
> > On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> > vijikarthi@yahoo.com.invalid> wrote:
> >
> >> I believe the HTTP API will use the same underlying message format
> (proto
> >> def) and hence the request/response value objects (java) needs to be
> >> auto-generated from the proto files for it to be used in Jersey based
> java
> >> rest client?
> >>
> >> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> >> janiszt@gmail.com> wrote:
> >>
> >>
> >> I suspect jar is deprecated and includes only old API used by mesoslib.
> >> The
> >> goal is to create HTTP API and stop supporting native libs (jars, so,
> >> etc).
> >> I think you shouldn't use that jar in your project.
> >>
> >> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> >> vijikarthi@yahoo.com> napisał:
> >>
> >> > Hello,
> >> >
> >> > I am writing a rest client for "operator APIs" and found that some of
> >> the
> >> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> >> > "include/mesos/v1/master/master.proto") are not included in the mesos
> >> jar
> >> > file. While investigating, I have found that the "Make" file does not
> >> > include these proto definition files.
> >> >
> >> > I have updated the Make file and added the protos that I am interested
> >> in
> >> > and built a new jar file. Is there any reason why these proto
> >> definitions
> >> > are not included in the original build apart from the reason that the
> >> APIs
> >> > are still evolving?
> >> >
> >> > Regards
> >> > Vijay
> >> >
> >>
> >> --
> >> Zameer Manji
> >>
> >
>
>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Vijay Srinivasaraghavan <vi...@yahoo.com>.
I have created a JIRA and will submit a patch. Could someone please add me to the contributor list as I am not able to assign the JIRA to myself?
https://issues.apache.org/jira/browse/MESOS-6597
On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar <an...@apache.org> wrote:
We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)
Please file an issue as Zameer pointed out.
-anand
On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> janiszt@gmail.com> wrote:
>>
>>
>> I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikarthi@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Vijay Srinivasaraghavan <vi...@yahoo.com.INVALID>.
I have created a JIRA and will submit a patch. Could someone please add me to the contributor list as I am not able to assign the JIRA to myself?
https://issues.apache.org/jira/browse/MESOS-6597
On Wednesday, November 16, 2016 9:00 AM, Anand Mazumdar <an...@apache.org> wrote:
We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)
Please file an issue as Zameer pointed out.
-anand
On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> janiszt@gmail.com> wrote:
>>
>>
>> I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikarthi@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Anand Mazumdar <an...@apache.org>.
We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)
Please file an issue as Zameer pointed out.
-anand
On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> janiszt@gmail.com> wrote:
>>
>>
>> I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikarthi@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Anand Mazumdar <an...@apache.org>.
We wanted to move the project away from officially supporting anything
other than C++ and discuss more on if we should be responsible for
publishing to the various language specific channels. However, for the time
being, we had decided to include the v1 protobufs in the mesos JAR itself.
(it already contains the v1 Scheduler/Executor protos)
Please file an issue as Zameer pointed out.
-anand
On Wed, Nov 16, 2016 at 8:34 AM, Zameer Manji <zm...@apache.org> wrote:
> I think this is a bug, I feel the jar should include all v1 protobuf files.
>
> Vijay, I encourage you to file a ticket.
>
> On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com.invalid> wrote:
>
>> I believe the HTTP API will use the same underlying message format (proto
>> def) and hence the request/response value objects (java) needs to be
>> auto-generated from the proto files for it to be used in Jersey based java
>> rest client?
>>
>> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
>> janiszt@gmail.com> wrote:
>>
>>
>> I suspect jar is deprecated and includes only old API used by mesoslib.
>> The
>> goal is to create HTTP API and stop supporting native libs (jars, so,
>> etc).
>> I think you shouldn't use that jar in your project.
>>
>> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
>> vijikarthi@yahoo.com> napisał:
>>
>> > Hello,
>> >
>> > I am writing a rest client for "operator APIs" and found that some of
>> the
>> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
>> > "include/mesos/v1/master/master.proto") are not included in the mesos
>> jar
>> > file. While investigating, I have found that the "Make" file does not
>> > include these proto definition files.
>> >
>> > I have updated the Make file and added the protos that I am interested
>> in
>> > and built a new jar file. Is there any reason why these proto
>> definitions
>> > are not included in the original build apart from the reason that the
>> APIs
>> > are still evolving?
>> >
>> > Regards
>> > Vijay
>> >
>>
>> --
>> Zameer Manji
>>
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Zameer Manji <zm...@apache.org>.
I think this is a bug, I feel the jar should include all v1 protobuf files.
Vijay, I encourage you to file a ticket.
On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
vijikarthi@yahoo.com.invalid> wrote:
> I believe the HTTP API will use the same underlying message format (proto
> def) and hence the request/response value objects (java) needs to be
> auto-generated from the proto files for it to be used in Jersey based java
> rest client?
>
> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> janiszt@gmail.com> wrote:
>
>
> I suspect jar is deprecated and includes only old API used by mesoslib.
> The
> goal is to create HTTP API and stop supporting native libs (jars, so, etc).
> I think you shouldn't use that jar in your project.
>
> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com> napisał:
>
> > Hello,
> >
> > I am writing a rest client for "operator APIs" and found that some of the
> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> > "include/mesos/v1/master/master.proto") are not included in the mesos
> jar
> > file. While investigating, I have found that the "Make" file does not
> > include these proto definition files.
> >
> > I have updated the Make file and added the protos that I am interested in
> > and built a new jar file. Is there any reason why these proto definitions
> > are not included in the original build apart from the reason that the
> APIs
> > are still evolving?
> >
> > Regards
> > Vijay
> >
>
> --
> Zameer Manji
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Zameer Manji <zm...@apache.org>.
I think this is a bug, I feel the jar should include all v1 protobuf files.
Vijay, I encourage you to file a ticket.
On Tue, Nov 15, 2016 at 8:04 PM, Vijay Srinivasaraghavan <
vijikarthi@yahoo.com.invalid> wrote:
> I believe the HTTP API will use the same underlying message format (proto
> def) and hence the request/response value objects (java) needs to be
> auto-generated from the proto files for it to be used in Jersey based java
> rest client?
>
> On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <
> janiszt@gmail.com> wrote:
>
>
> I suspect jar is deprecated and includes only old API used by mesoslib.
> The
> goal is to create HTTP API and stop supporting native libs (jars, so, etc).
> I think you shouldn't use that jar in your project.
>
> wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
> vijikarthi@yahoo.com> napisał:
>
> > Hello,
> >
> > I am writing a rest client for "operator APIs" and found that some of the
> > protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> > "include/mesos/v1/master/master.proto") are not included in the mesos
> jar
> > file. While investigating, I have found that the "Make" file does not
> > include these proto definition files.
> >
> > I have updated the Make file and added the protos that I am interested in
> > and built a new jar file. Is there any reason why these proto definitions
> > are not included in the original build apart from the reason that the
> APIs
> > are still evolving?
> >
> > Regards
> > Vijay
> >
>
> --
> Zameer Manji
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Vijay Srinivasaraghavan <vi...@yahoo.com>.
I believe the HTTP API will use the same underlying message format (proto def) and hence the request/response value objects (java) needs to be auto-generated from the proto files for it to be used in Jersey based java rest client?
On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <ja...@gmail.com> wrote:
I suspect jar is deprecated and includes only old API used by mesoslib. The
goal is to create HTTP API and stop supporting native libs (jars, so, etc).
I think you shouldn't use that jar in your project.
wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> napisał:
> Hello,
>
> I am writing a rest client for "operator APIs" and found that some of the
> protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> "include/mesos/v1/master/master.proto") are not included in the mesos jar
> file. While investigating, I have found that the "Make" file does not
> include these proto definition files.
>
> I have updated the Make file and added the protos that I am interested in
> and built a new jar file. Is there any reason why these proto definitions
> are not included in the original build apart from the reason that the APIs
> are still evolving?
>
> Regards
> Vijay
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Vijay Srinivasaraghavan <vi...@yahoo.com.INVALID>.
I believe the HTTP API will use the same underlying message format (proto def) and hence the request/response value objects (java) needs to be auto-generated from the proto files for it to be used in Jersey based java rest client?
On Tuesday, November 15, 2016 12:37 PM, Tomek Janiszewski <ja...@gmail.com> wrote:
I suspect jar is deprecated and includes only old API used by mesoslib. The
goal is to create HTTP API and stop supporting native libs (jars, so, etc).
I think you shouldn't use that jar in your project.
wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> napisał:
> Hello,
>
> I am writing a rest client for "operator APIs" and found that some of the
> protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> "include/mesos/v1/master/master.proto") are not included in the mesos jar
> file. While investigating, I have found that the "Make" file does not
> include these proto definition files.
>
> I have updated the Make file and added the protos that I am interested in
> and built a new jar file. Is there any reason why these proto definitions
> are not included in the original build apart from the reason that the APIs
> are still evolving?
>
> Regards
> Vijay
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Tomek Janiszewski <ja...@gmail.com>.
I suspect jar is deprecated and includes only old API used by mesoslib. The
goal is to create HTTP API and stop supporting native libs (jars, so, etc).
I think you shouldn't use that jar in your project.
wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> napisał:
> Hello,
>
> I am writing a rest client for "operator APIs" and found that some of the
> protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> "include/mesos/v1/master/master.proto") are not included in the mesos jar
> file. While investigating, I have found that the "Make" file does not
> include these proto definition files.
>
> I have updated the Make file and added the protos that I am interested in
> and built a new jar file. Is there any reason why these proto definitions
> are not included in the original build apart from the reason that the APIs
> are still evolving?
>
> Regards
> Vijay
>
Re: Mesos V1 Operator HTTP API - Java Proto Classes
Posted by Tomek Janiszewski <ja...@gmail.com>.
I suspect jar is deprecated and includes only old API used by mesoslib. The
goal is to create HTTP API and stop supporting native libs (jars, so, etc).
I think you shouldn't use that jar in your project.
wt., 15.11.2016, 20:38 użytkownik Vijay Srinivasaraghavan <
vijikarthi@yahoo.com> napisał:
> Hello,
>
> I am writing a rest client for "operator APIs" and found that some of the
> protobuf java classes (like "include/mesos/v1/quota/quota.proto",
> "include/mesos/v1/master/master.proto") are not included in the mesos jar
> file. While investigating, I have found that the "Make" file does not
> include these proto definition files.
>
> I have updated the Make file and added the protos that I am interested in
> and built a new jar file. Is there any reason why these proto definitions
> are not included in the original build apart from the reason that the APIs
> are still evolving?
>
> Regards
> Vijay
>