[
https://issues.apache.org/jira/browse/TUBEMQ-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243123#comment-17243123
]
ASF subversion and git services commented on TUBEMQ-439:
--------------------------------------------------------
Commit be4bdf06d099047d4d56ac9fa984f98135fefc03 in incubator-tubemq's branch
refs/heads/TUBEMQ-430 from gosonzhang
[ https://gitbox.apache.org/repos/asf?p=incubator-tubemq.git;h=be4bdf0 ]
[TUBEMQ-439]Add Cli field Scheme definition (#335)
Co-authored-by: gosonzhang <[email protected]>
> Add Cli field Scheme definition
> -------------------------------
>
> Key: TUBEMQ-439
> URL: https://issues.apache.org/jira/browse/TUBEMQ-439
> Project: Apache TubeMQ
> Issue Type: Sub-task
> Components: Server
> Reporter: Guocheng Zhang
> Assignee: Guocheng Zhang
> Priority: Major
> Labels: pull-request-available
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> It is found that the field tokens used to interact with users in CLI or HTTP
> API requests have a relatively large overlap. This issue is hoped that a
> unified field output goal can be achieved through the field definition
> scheme, and the same attribute has a unified attribute definition and
> interpretation, which reduces the user's learning and use cost To maintain
> the consistency of interface interaction
> Because CLI and HTTP API are not a complete closed loop, and there are still
> compatibility issues, the existing ones are defined first, and then the new
> field definitions and interfaces will be gradually standardized. When
> appropriate, we will update the outdated interfaces.
> It should be noted that after the version is released, the existing
> definition fields in scheme cannot be modified, only new fields can be added
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
