It's already deprecated. No one is encouraged to use v1 API except for
users for Pulsar 1.x that had topics created with the old namings.
What I'm proposing, instead of trying to fix the inconsistencies in
that API, is to disable v1 API by default and leave a configuration
option to turn it on in
> Having said that, V1 admin API was in effect considered as "soft
deprecated" since Pulsar 2.0. All documentation has been focused on v2 APIs.
There are Orgs which have large scale Pulsar clusters and use V1 apis.
There is no way we can deprecate V1 api and it has to be maintained until
we find
Thanks.
@Matteo I will track this.
Regards
Jiwei Guo (Tboy)
On Tue, May 10, 2022 at 7:37 AM Matteo Merli wrote:
> Why I agree that it "looks like a bug", "walks like a bug" and "talks
> like a bug"...
> this was actually a "feature" :)
>
> not a good one, or with a good reason to exist, but
Why I agree that it "looks like a bug", "walks like a bug" and "talks
like a bug"...
this was actually a "feature" :)
not a good one, or with a good reason to exist, but something we've
been trying not to break. I'm not going to dig into the "wrong"
reasoning on why this was done in the first
+1
I agree totally. It is a bug
Enrico
Il Lun 9 Mag 2022, 20:59 Michael Marshall ha scritto:
> Great find, Jiwei Guo. I agree that this should be classified as a bug
> and that we should change the V1 implementation so that a topic can
> only be created if its namespace already exists.
>
>
Great find, Jiwei Guo. I agree that this should be classified as a bug
and that we should change the V1 implementation so that a topic can
only be created if its namespace already exists.
Thanks,
Michael
On Mon, May 9, 2022 at 7:13 AM guo jiwei wrote:
>
> Hi, community:
>I found that in the
