We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Ubuntu
code the develop branch
1.8.0
https://github.com/apache/rocketmq/blob/develop/broker/src/main/java/org/apache/rocketmq/broker/topic/TopicConfigManager.java#L333C1-L333C1
the code "enableSingleTopicRegister" is removed when merge "support rocksdb kv storage"
None
No response
The text was updated successfully, but these errors were encountered:
[ISSUE #7302] Fix singleTopicRegister code deleted in merge
d67b9d6
Successfully merging a pull request may close this issue.
Before Creating the Bug Report
I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.
Runtime platform environment
Ubuntu
RocketMQ version
code the develop branch
JDK Version
1.8.0
Describe the Bug
https://github.com/apache/rocketmq/blob/develop/broker/src/main/java/org/apache/rocketmq/broker/topic/TopicConfigManager.java#L333C1-L333C1
the code "enableSingleTopicRegister" is removed when merge "support rocksdb kv storage"
Steps to Reproduce
None
What Did You Expect to See?
None
What Did You See Instead?
None
Additional Context
No response
The text was updated successfully, but these errors were encountered: