You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tubemq.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2021/03/19 02:26:00 UTC
[jira] [Updated] (TUBEMQ-570) Optimizing the implementations of
HTTP API for Master
[ https://issues.apache.org/jira/browse/TUBEMQ-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guocheng Zhang updated TUBEMQ-570:
----------------------------------
Description:
At present, there are some problems in the HTTP API implementation, such as API encapsulation is not perfect, readability is poor, and some consumption related metrics are missing
Append:
due to the LICENSE problem of BDB, we need to adjust from the bottom metadata manage to the WEB API implements
In order to ensure that the system can be switched seamlessly, the abstraction of storage and active/standby keep-alive services will be performed first, and then support can be switched to zk or other storage components
was:At present, there are some problems in the HTTP API implementation, such as API encapsulation is not perfect, readability is poor, and some consumption related metrics are missing
> Optimizing the implementations of HTTP API for Master
> -----------------------------------------------------
>
> Key: TUBEMQ-570
> URL: https://issues.apache.org/jira/browse/TUBEMQ-570
> Project: Apache TubeMQ
> Issue Type: Improvement
> Components: Master
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
>
> At present, there are some problems in the HTTP API implementation, such as API encapsulation is not perfect, readability is poor, and some consumption related metrics are missing
>
> Append:
> due to the LICENSE problem of BDB, we need to adjust from the bottom metadata manage to the WEB API implements
> In order to ensure that the system can be switched seamlessly, the abstraction of storage and active/standby keep-alive services will be performed first, and then support can be switched to zk or other storage components
--
This message was sent by Atlassian Jira
(v8.3.4#803005)