Hi,
> 1. use produce authentication, small changes, and compatibility with
the original mode. But it's not clear and not flexible enough
I'm +1 for this solution.
Thanks.
Zike Yang
On Mon, Oct 17, 2022 at 11:21 AM Zixuan Liu wrote:
>
> > I prefer to use the produce authentication because it do
> I prefer to use the produce authentication because it doesn't affect
the existing authentication policy.
I agree with this idea.
Thanks,
Zixuan
丛搏 于2022年10月17日周一 10:07写道：
> Hi Enrico:
>
> Enrico Olivelli 于2022年10月13日周四 17:31写道：
> >
> > Bo,
> >
> > Il giorno gio 13 ott 2022 alle ore 06:00 丛
Hi Enrico:
Enrico Olivelli 于2022年10月13日周四 17:31写道：
>
> Bo,
>
> Il giorno gio 13 ott 2022 alle ore 06:00 丛搏 ha scritto:
> >
> > Hello, Pulsar community:
> >
> > Now, we have two authentications for updating the schema
> > 1. producer and consumer can update the schema using TopicOperation
> > pro
Bo,
Il giorno gio 13 ott 2022 alle ore 06:00 丛搏 ha scritto:
>
> Hello, Pulsar community:
>
> Now, we have two authentications for updating the schema
> 1. producer and consumer can update the schema using TopicOperation
> produce or consume when open autoUpdateSchema
> 2. pulsar admin uses Tenant
