You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@inlong.apache.org by "Guocheng Zhang (Jira)" <ji...@apache.org> on 2021/08/23 09:05:00 UTC
[jira] [Updated] (INLONG-570) Optimizing the implementations of
HTTP API for Master
[ https://issues.apache.org/jira/browse/INLONG-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guocheng Zhang updated INLONG-570:
----------------------------------
Fix Version/s: 0.10.0
> Optimizing the implementations of HTTP API for Master
> -----------------------------------------------------
>
> Key: INLONG-570
> URL: https://issues.apache.org/jira/browse/INLONG-570
> Project: Apache InLong
> Issue Type: Improvement
> Components: inlong-tubemq
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.10.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> 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)