You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Thomas Jamet <tj...@subjectiv.io> on 2020/05/09 11:58:03 UTC

Pulsar Admin Api

Hello,
I have downloaded Pulsar 2.5.0 recently and I am using it through the
Python client.
I also generated a Python client for the Pulsar Admin REST API (v2) using
the OpenAPI specification (http://pulsar.apache.org/admin-rest-api/).

In a couple of instances, I had to patch the specification because it
seemed to me that it was not complete:

- the PUT /namespaces/{tenant}/{namespace} command had a missing in/body
parameter for policies
- the GET /non-persistent/{tenant}/{namespace}/{topic}/lastMessageId, POST
/non-persistent/{tenant}/{namespace}/{topic}/terminate, GET
/persistent/{tenant}/{namespace}/{topic}/lastMessageId and POST
/persistent/{tenant}/{namespace}/{topic}/terminate commands specified a
MessageId object in their response, but the MessageId object definition has
no property unlike the MessageIdImpl object definition.

This is my first post to this group, so please could somebody guide me on
how to report these kinds of issues?
Also, is this the best mailing list to ask general questions about best
practices when designing a system based on Pulsar?

Thanks,
Thomas

Re: Pulsar Admin Api

Posted by Sijie Guo <gu...@gmail.com>.
You can report issues by creating issues at Pulsar github repo:
https://github.com/apache/pulsar.

Mailing list is a good place to ask questions.

- Sijie

On Sat, May 9, 2020 at 4:58 AM Thomas Jamet <tj...@subjectiv.io> wrote:

> Hello,
> I have downloaded Pulsar 2.5.0 recently and I am using it through the
> Python client.
> I also generated a Python client for the Pulsar Admin REST API (v2) using
> the OpenAPI specification (http://pulsar.apache.org/admin-rest-api/).
>
> In a couple of instances, I had to patch the specification because it
> seemed to me that it was not complete:
>
> - the PUT /namespaces/{tenant}/{namespace} command had a missing in/body
> parameter for policies
> - the GET /non-persistent/{tenant}/{namespace}/{topic}/lastMessageId, POST
> /non-persistent/{tenant}/{namespace}/{topic}/terminate, GET
> /persistent/{tenant}/{namespace}/{topic}/lastMessageId and POST
> /persistent/{tenant}/{namespace}/{topic}/terminate commands specified a
> MessageId object in their response, but the MessageId object definition has
> no property unlike the MessageIdImpl object definition.
>
> This is my first post to this group, so please could somebody guide me on
> how to report these kinds of issues?
> Also, is this the best mailing list to ask general questions about best
> practices when designing a system based on Pulsar?
>
> Thanks,
> Thomas
>