rocketmq: back-incompatible the RequestCode(`REGISTER_TOPIC_IN_NAMESRV`) with `217` value
- Please describe the issue you observed:
There was described the 217 code as GET_KV_CONFIG_BY_VALUE label, see here
GET_KV_CONFIG_BY_VALUE = 217,
But since 5.0.0-beta, the RequestCode(217) may be reusable as REGISTER_TOPIC_IN_NAMESRV
Those two kind of RemotingCommand operations looks like incompatible, the one GET_KV_CONFIG_BY_VALUE mostly same as fetching and another REGISTER_TOPIC_IN_NAMESRV sames to pushing.
It’s suggest that toggle the REGISTER_TOPIC_IN_NAMESRV code to another one for the back compatible.
About this issue
- Original URL
- State: open
- Created 2 years ago
- Comments: 15 (11 by maintainers)
Commits related to this issue
- [#5768] changed code of REGISTER_TOPIC_IN_NAMESRV to 1217 — committed to Abhijeetmishr/rocketmq by Abhijeetmishr a year ago
@Abhijeetmishr
REGISTER_TOPIC_IN_NAMESRVwas added on 5.0+ version, but there were a lot of historic versions from 3.x to 4.x. In my opinion, toggle the oneREGISTER_TOPIC_IN_NAMESRVto another code shall be a good choice.Searching the github with GET_KV_CONFIG_BY_VALUE with language Java, there were a lots of
public static final int GET_KV_CONFIG_BY_VALUE = 217;definitions on the rocketmq previous versions. TheGET_KV_CONFIG_BY_VALUEis not a newRequestCode, It was already exists.I think the code 217 was inappropriated mapping to
REGISTER_TOPIC_IN_NAMESRVsince 5.0.0-beta and sugguest that creating a new code, eg: something like1217for theREGISTER_TOPIC_IN_NAMESRV.@Abhijeetmishr
cc @aaron-ai
Sure, I assigned it to you 😃
Sure, I’m not good at JAVA and glad to see it is solved.