+1 for dropping the schema when a topic is deleted by default. I previously met a strange error that after creating a topic with the same name as previous deleted topic, the "ghost" schema is associated with the new topic again and caused a lot of confusion for us.
On 2021/11/18 03:35:50 Ruguo Yu wrote: > Hi All, > > > After discussing with Penghui and HangChen about the consistency of topic and > schema deletion, our preliminary conclusion is to drop the `--deleteSchema` > parameter in `bin/pulsar-admin topics delete`, which can ensure the schema is > deleted when the topic is deleted, and the default value is `true` on the > broker side to be compatible with the lower version client’s deletion request. > This change plan to be merged in the next major version release. What about > your thoughts on this? > > > Thanks, > > Ruguo Yu > > > > On 2021/11/14 14:14:52 yuruguo wrote: > > > Dear all, > > > > > > Currently, topic and schema are managed separately, and there will be a > > situation, that is, the topic has been deleted but its schema still exists. > > Should we deal with these residual schemas? For this problem I created an > > issue[1]. > > > > > > In addition, the operation auth of the schema should also converge. To a > > certain extent, it is related to the operation auth of topic. For this > > problem I created an issue[2]. > > > > > > Regarding the two problems of the schema, please give guidance or a better > > solution 😊 > > > > > > > > > > > > [1] https://github.com/apache/pulsar/issues/12795 > > > > > > [2] https://github.com/apache/pulsar/issues/12419 > > > > > > > > > Thanks, > > > Ruguo Yu > > > > > > > > > > >
