Skip to content
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

[Doc] compatibility naming rule for the retry topic #20612

Closed
1 of 2 tasks
poorbarcode opened this issue Jun 20, 2023 · 1 comment · Fixed by apache/pulsar-site#651
Closed
1 of 2 tasks

[Doc] compatibility naming rule for the retry topic #20612

poorbarcode opened this issue Jun 20, 2023 · 1 comment · Fixed by apache/pulsar-site#651
Labels
doc-required Your PR changes impact docs and you will update later. Stale

Comments

@poorbarcode
Copy link
Contributor

Search before asking

  • I searched in the issues and found nothing similar.

What issue do you find in Pulsar docs?

The default naming rule of Retry topic is {tenant}/{namespaces}/{topic}-{sub}-RETRY, see: https://pulsar.apache.org/docs/3.0.x/concepts-messaging/#retry-letter-topic

The rule before version 2.8 was {tenant}/{namespaces}/{sub}-RETRY, and if there is a ZK node /admin/partitioned-topics/{namespace}-RETRY, Pulsar will still use the rule {tenant}/{namespaces}/{sub}-RETRY even if the version of Pulsar is larger than 2.8. This part of the explanation is not reflected in the documentation.

Related PR

What is your suggestion?

Remove this compatibility logic or add a document that explains it.

Any reference?

Are you willing to submit a PR?

  • I'm willing to submit a PR!
@poorbarcode poorbarcode added the doc-required Your PR changes impact docs and you will update later. label Jun 20, 2023
@github-actions
Copy link

The issue had no activity for 30 days, mark with Stale label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
doc-required Your PR changes impact docs and you will update later. Stale
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant