-
Notifications
You must be signed in to change notification settings - Fork 561
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
Regression: rpk topic consume --regex
never works
#18602
Comments
Thanks for bringing this up. We will fix this soon. |
r-vasquez
added a commit
to r-vasquez/redpanda
that referenced
this issue
May 22, 2024
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
May 22, 2024
Fixes redpanda-data#18602 (cherry picked from commit 6736747)
vbotbuildovich
pushed a commit
to vbotbuildovich/redpanda
that referenced
this issue
May 22, 2024
Fixes redpanda-data#18602 (cherry picked from commit 6736747)
Lazin
pushed a commit
to Lazin/redpanda
that referenced
this issue
Jun 1, 2024
Lazin
pushed a commit
to Lazin/redpanda
that referenced
this issue
Jun 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version & Environment
Redpanda version: (use
rpk version
): 23.3.12What went wrong?
rpk topic consume --regex
always fails if any non-literal chars are used. For example, the following command against a broker with at least one topic should return data instead of failing:It looks like this regressed in #13330, which validates that topics exist before consuming them, but when
--regex
is passed the topics are to be interpreted as patterns instead of literal values.What should have happened instead?
--regex
flag should disable the topic existence validation added in #13330How to reproduce the issue?
rpk topic consume --regex '.*'
UNKNOWN_TOPIC_OR_PARTITION
errorJIRA Link: CORE-3047
The text was updated successfully, but these errors were encountered: