On Tue, Feb 14, 2023 at 3:46 AM <mattisonc...@gmail.com> wrote: > Hi, Asaf > > Welcome to join this discussion. > > You mean that allows the *system* to use it when it's a partitioned > topic? > Sorry, I didn't get your point. What do you mean by *system*? >
This sentence was a reply to: 2. Make the `-partition-` string the keyword. That allows the user to use > it when it's a partitioned topic. > I wanted to say that this sentence should be: Make the `-partition-` string the keyword, that allows the *system* to use it when it's a partitioned topic. > > Why postfix of `__`?Why uppercase ?Maybe `__system__<name>`? > Yes, That is a key point that I want to discuss in this > thread. `__system__<name>` is good for me. > > Can you please elaborate what it means to make it dynamic exactly? > Sorry, I will refine it. it means we can update this configuration > dynamically. (using rest api or sth) > I'm unfamiliar with how Pulsar supports dynamic configuration. I would love it if you can share a link or explain it briefly, thus explaining what exactly you are going to change to support dynamic configuration. > General question: In the last thread you said something about > configurablerules, etc? You decided not to use this idea? > IMO, That idea is an advanced feature. we may need more time to discuss > the details and for the topic name restriction, maybe we don't have strong > reason to use that. > > We can introduce this advanced feature when we have a need for it. > > WDYT? > I agree. Future PIP and discussion. > > Best, > Mattison > On Feb 13, 2023, 22:21 +0800, Asaf Mesika <asaf.mes...@gmail.com>, wrote: > > You mean that allows the *system* to use it when it's a partitioned > topic? >
