EliHarper opened a new issue #8582: URL: https://github.com/apache/pulsar/issues/8582
**Describe the bug** While I'm not sure which version is right (--topics-pattern & --topics-Pattern are listed in documentation, --topicsPattern also mentioned in man-style error messages and I _think_ I saw --topic-pattern elsewhere), I created a sink that passed both micro_.* and micro_*; neither of which matched any of the expected pulsar topics. **To Reproduce** 1. Run pulsar-all docker image on CentOS 7 2. Create a Cassandra container as specified [here](https://pulsar.apache.org/docs/en/io-quickstart/#setup-a-cassandra-cluster) 3. Configure Pulsar sink as specified [here ](https://pulsar.apache.org/docs/en/io-quickstart/#configure-a-cassandra-sink) 4. Create a Cassandra sink using the --topics-pattern argument matching multiple topics with similar prefixes, ending with a wildcard. 5. See if any messages are read from the topic - none showed for me in the database or using pulsar-admin sinks status. **Expected behavior** Pulsar messages from all matching topics read from pulsar and recorded in the Cassandra sink. **Desktop (please complete the following information):** - OS: CentOS 7, Docker version 19.03.13, build 4484c46d9d **Additional context** I'm honestly fairly new to Pulsar. If I'm doing anything wrong, please correct me; I just believe this seems to be a bug since the same sink creation command worked when I used the --inputs argument instead with an explicit topic name. (in this example, micro_aggregator) Thank you! ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
