+1 (non-binding)
houxiaoyu 于2022年9月29日周四 16:45写道：
> +1 (non-binding)
>
> - Checksum and signatures
> - Build on Mac, using JDK17
> - Run Pulsar standalone and produce/consume case
>
> Thanks,
> Xiaoyu Hou
>
> Enrico Olivelli 于2022年9月29日周四 16:31写道：
>
> > +1 (binding)
> > - Apache RAT
> > - Signa
+1
Paul Gier 于2022年10月1日周六 05:41写道：
> I thought about this a bit more and realized that ldflags doesn't really
> make sense in this case because this is a library, and we don't control the
> user's build environment. It might work fine for the pulsar-perf binary,
> but doesn't really make sense
> Overall, I support setting naming restrictions on topic name and
> subscription name.
> But we must consider the compatibility since it would be a big break
change.
> One possible option would be adding a config entry in broker.conf for
> the naming regex on topic and
> subscriptions, with defaul
> The namespace, cluster and topic names are checked by the
org.apache.pulsar.common.naming.NamedEntity#checkName method, which
requires names to contain only (a-zA-Z_0-9) or these special chars -=:.% .
Sorry, the description is wrong here.
The namespace, cluster names are checked by the
org.apach
> I think the subscription name should not contain special characters. It
should keep the same naming rule with the topic.
The namespace, cluster and topic names are checked by the
org.apache.pulsar.common.naming.NamedEntity#checkName method, which
requires names to contain only (a-zA-Z_0-9) or th
> I think the subscription name should not contain special characters. It
> should keep the same naming rule with the topic.
Currently, we have entify naming restrictions on
cluster/tenant/namespace, but not on topic names, see [1].
We can create topics like "persistent://public/default/###".
Ove
