Hi Dianjin,
Thanks for your reminder!
Please check my application here (
https://docs.google.com/document/d/1fSVi1ELO7hGSF6_Cm1O9A-kw7covij882_cajLg4Jzs/edit#),
which is more user-friendly to read and re-use info.
Also, attach here for your quick reference.
English Version
# Pr
This is the third release candidate for Apache Pulsar, version 3.0.0.
It fixes the following issues:
https://github.com/apache/pulsar/milestone/34?closed=1
*** Please download, test and vote on this release. This vote will
stay open for at least 72 hours ***
Note that we are voting upon the sour
I have a PR that aims to be included in this release:
https://github.com/apache/pulsar-client-cpp/pull/257. It's mainly
added to solve the issue that the Python client might not consume Avro
messages sent with different schemas, e.g. the fields order changed.
The Python client needs this API to ret
Hi Girish and Zike,
@Girish,
Regarding your question about the scope of the regex-based deletion
feature, the initial proposal is to delete the specified topics or
namespaces only in the local cluster where the command is run. If you
need to delete them in remote clusters as well, you can simply r
Hi, Xiangying
> 1. I understand that one of your concerns is whether the proposed
> regex-based deletion feature would provide significant advantages over
> using a simple one-liner script to call the delete topic command for
> each topic. As Yubiao pointed out, using scripts to delete topics one
Hi, Yubiao,
> It took us a long time to
> remove these topics. We delete these topics in this way:
> ```
> cat topics_name_file | awk '{system("bin/pulsar-admin topics delete "$0)}'
> )
> ```
> It deletes topics one by one.
The main overhead here is the frequent creation and release of the JVM.
