> Which are the downsides of enabling system topics? No obvious downsides, just created a __change_events topic under each namespace and the broker created a reader to read new messages from it. Looks like introducing some idle topics and idle readers if users will not use the topic policy.
And transactions will also need the system topic feature. Penghui On Tue, Apr 26, 2022 at 10:27 PM Zike Yang <z...@apache.org> wrote: > +1 > > Please update this PIP number. It's duplicated with > https://github.com/apache/pulsar/issues/15207 > > Zike > > On Tue, Apr 26, 2022 at 8:09 PM Enrico Olivelli <eolive...@gmail.com> > wrote: > > > > Which are the downsides of enabling system topics? > > > > Enrico > > > > Il Mar 26 Apr 2022, 14:07 guo jiwei <techno...@apache.org> ha scritto: > > > > > Hi community: > > > In PIP-39 > > > < > https://github.com/apache/pulsar/wiki/PIP-39%3A-Namespace-Change-Events>, > > > we have introduced namespace event to support topic level policy. This > > > feature was released in Pulsar 2.6. > > > > > > Then PIP-92 > > > < > > > > https://github.com/apache/pulsar/wiki/PIP-92%3A-Topic-policy-across-multiple-clusters > > > >, > > > we support topic policy to replicate across clusters and release in > Pulsar > > > 2.10. > > > > > > And with version iteration, the corresponding topic policy CLI and > > > functions are mature and stable, but users need to enable system topic > to > > > support these features. So it's better to enable system topic by > default. > > > > > > > > > So I have opened apache/pulsar#15333 > > > <https://github.com/apache/pulsar/issues/15333> to discuss this. > > > > > > > > > Regards > > > Jiwei Guo (Tboy) > > > >
