-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Subscription to topics with regex not working for non-persisten topics #6845
Comments
@itaross Can you provide more details about the bug? what version are you using and how to reproduce it. This will help to troubleshoot this issue. |
I am currently using version 2.5.1 This has been highlighted also in the previous cited issued, but it has not been addressed in sinks. Everything works if you you use persistent topics. |
@codelipenghui have you been able to reproduce? This is something that I think has never worked, but very useful |
Can you provide a way to reproduce? In functions, sinks and sources, |
@wolfstudy what you are referring to is probably this line https://github.com/oncodeit/pulsar/blob/71b3819bfc11afe0f0da19df0a19e3b7a05988c5/pulsar-client-tools/src/main/java/org/apache/pulsar/admin/cli/CmdSinks.java#L258 To reproduce: take any connector from Pulsar IO, a sink in this case. Follow these steps: https://pulsar.apache.org/docs/en/standalone/#install-builtin-connectors-optional Launch the connector with:
content of the yaml:
then retry using:
You will notice that the connector will now works. I posted this example with jdbc/mysql but you can try with anything you prefer, the behaviour is the same. |
Hi @wolfstudy, any update on this? May I help with this? |
@codelipenghui @wolfstudy Has there been any update on this? I am seeing the same in 2.9.1 |
Messages on non-persistent topics are not received when using a regex subscription.
This problem is encountered when using a Pulsar IO custom connector (sink).
When using persistent topics the subscription is working as expected
Expected behavior
Records are received when subscribing to regex topics.
Additional context
Issues #2009
#2009
Issues #2025
#2025
Does not solve this problem
@merlimat @sijie
The text was updated successfully, but these errors were encountered: