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 authentication
This will produce problems when using different authentications to update the schema. There are two solutions here: 1. use produce authentication, small changes, and compatibility with the original mode. But it's not clear and not flexible enough 2. add single update schema authentication in TopicOperation. Big changes, not compatible with the original mode, but more clear and flexible I prefer to use the produce authentication because it doesn't affect the existing authentication policy. I hope you can discuss and provide your own views Thanks, Bo
