You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@inlong.apache.org by gi...@apache.org on 2021/04/23 04:01:31 UTC
[incubator-inlong-website] branch asf-site updated: Automated
deployment: Fri Apr 23 04:01:22 UTC 2021
f1213a769f9f2c2a7e7729e1d70e4b2291484b60
This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/incubator-inlong-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new f815e3b Automated deployment: Fri Apr 23 04:01:22 UTC 2021 f1213a769f9f2c2a7e7729e1d70e4b2291484b60
f815e3b is described below
commit f815e3b36699c215b9a2e8d55f690a6ad0c46a38
Author: wf123537200 <wf...@users.noreply.github.com>
AuthorDate: Fri Apr 23 04:01:22 2021 +0000
Automated deployment: Fri Apr 23 04:01:22 UTC 2021 f1213a769f9f2c2a7e7729e1d70e4b2291484b60
---
.asf.yaml | 12 +-
docs/en-us/architecture.md | 12 +-
docs/en-us/client_rpc.md | 16 +-
docs/en-us/clients_java.md | 24 +--
docs/en-us/configure_introduction.md | 12 +-
docs/en-us/console_introduction.md | 24 +--
docs/en-us/consumer_example.md | 4 +-
docs/en-us/contact.md | 8 +-
docs/en-us/deployment.md | 26 +--
.../en-us/development/how-to-become-a-committer.md | 22 +--
docs/en-us/development/how-to-commit.md | 46 +++---
docs/en-us/development/how-to-contribute.md | 28 ++--
docs/en-us/development/how-to-release.md | 158 +++++++++----------
docs/en-us/development/how-to-subscribe.md | 26 +--
docs/en-us/development/how-to-use-jira.md | 16 +-
docs/en-us/development/how-to-verify.md | 26 +--
.../development/how-to-vote-a-committer-ppmc.md | 24 +--
docs/en-us/download/download.md | 34 ++--
docs/en-us/download/release-0.3.0.md | 94 +++++------
docs/en-us/download/release-0.5.0.md | 174 ++++++++++-----------
docs/en-us/download/release-0.6.0.md | 46 +++---
docs/en-us/download/release-0.7.0.md | 62 ++++----
docs/en-us/download/release-0.8.0.md | 150 +++++++++---------
docs/en-us/error_code.md | 6 +-
docs/en-us/http_access_api.md | 4 +-
docs/en-us/producer_example.md | 4 +-
docs/en-us/quick_start.md | 84 +++++-----
docs/en-us/tubemq_perf_test_vs_Kafka_cn.md | 82 +++++-----
docs/zh-cn/architecture.md | 36 ++---
docs/zh-cn/client_rpc.md | 14 +-
docs/zh-cn/clients_java.md | 24 +--
docs/zh-cn/configure_introduction.md | 18 +--
docs/zh-cn/console_introduction.md | 24 +--
docs/zh-cn/consumer_example.md | 4 +-
docs/zh-cn/contact.md | 8 +-
docs/zh-cn/deployment.md | 26 +--
.../zh-cn/development/how-to-become-a-committer.md | 22 +--
docs/zh-cn/development/how-to-commit.md | 46 +++---
docs/zh-cn/development/how-to-contribute.md | 38 ++---
docs/zh-cn/development/how-to-release.md | 158 +++++++++----------
docs/zh-cn/development/how-to-subscribe.md | 26 +--
docs/zh-cn/development/how-to-use-jira.md | 16 +-
docs/zh-cn/development/how-to-verify.md | 26 +--
.../development/how-to-vote-a-committer-ppmc.md | 24 +--
docs/zh-cn/download/download.md | 34 ++--
docs/zh-cn/download/release-0.3.0.md | 94 +++++------
docs/zh-cn/download/release-0.5.0.md | 174 ++++++++++-----------
docs/zh-cn/download/release-0.6.0.md | 46 +++---
docs/zh-cn/download/release-0.7.0.md | 62 ++++----
docs/zh-cn/download/release-0.8.0.md | 150 +++++++++---------
docs/zh-cn/error_code.md | 6 +-
docs/zh-cn/http_access_api.md | 4 +-
docs/zh-cn/producer_example.md | 4 +-
docs/zh-cn/quick_start.md | 82 +++++-----
docs/zh-cn/tubemq_perf_test_vs_Kafka_cn.md | 82 +++++-----
en-us/community/index.html | 2 +-
en-us/docs/architecture.html | 12 +-
en-us/docs/architecture.json | 4 +-
en-us/docs/architecture.md | 12 +-
en-us/docs/client_rpc.html | 16 +-
en-us/docs/client_rpc.json | 4 +-
en-us/docs/client_rpc.md | 16 +-
en-us/docs/clients_java.html | 24 +--
en-us/docs/clients_java.json | 4 +-
en-us/docs/clients_java.md | 24 +--
en-us/docs/configure_introduction.html | 12 +-
en-us/docs/configure_introduction.json | 4 +-
en-us/docs/configure_introduction.md | 12 +-
en-us/docs/console_introduction.html | 24 +--
en-us/docs/console_introduction.json | 4 +-
en-us/docs/console_introduction.md | 24 +--
en-us/docs/consumer_example.html | 4 +-
en-us/docs/consumer_example.json | 4 +-
en-us/docs/consumer_example.md | 4 +-
en-us/docs/contact.html | 14 +-
en-us/docs/contact.json | 4 +-
en-us/docs/contact.md | 8 +-
en-us/docs/deployment.html | 26 +--
en-us/docs/deployment.json | 4 +-
en-us/docs/deployment.md | 26 +--
.../development/how-to-become-a-committer.html | 22 +--
.../development/how-to-become-a-committer.json | 4 +-
.../docs/development/how-to-become-a-committer.md | 22 +--
en-us/docs/development/how-to-commit.html | 46 +++---
en-us/docs/development/how-to-commit.json | 4 +-
en-us/docs/development/how-to-commit.md | 46 +++---
en-us/docs/development/how-to-contribute.html | 28 ++--
en-us/docs/development/how-to-contribute.json | 4 +-
en-us/docs/development/how-to-contribute.md | 28 ++--
en-us/docs/development/how-to-release.html | 158 +++++++++----------
en-us/docs/development/how-to-release.json | 4 +-
en-us/docs/development/how-to-release.md | 158 +++++++++----------
en-us/docs/development/how-to-subscribe.html | 38 ++---
en-us/docs/development/how-to-subscribe.json | 4 +-
en-us/docs/development/how-to-subscribe.md | 26 +--
en-us/docs/development/how-to-use-jira.html | 16 +-
en-us/docs/development/how-to-use-jira.json | 4 +-
en-us/docs/development/how-to-use-jira.md | 16 +-
en-us/docs/development/how-to-verify.html | 24 +--
en-us/docs/development/how-to-verify.json | 4 +-
en-us/docs/development/how-to-verify.md | 26 +--
.../development/how-to-vote-a-committer-ppmc.html | 24 +--
.../development/how-to-vote-a-committer-ppmc.json | 4 +-
.../development/how-to-vote-a-committer-ppmc.md | 24 +--
en-us/docs/download/download.html | 34 ++--
en-us/docs/download/download.json | 4 +-
en-us/docs/download/download.md | 34 ++--
en-us/docs/download/release-0.3.0.html | 94 +++++------
en-us/docs/download/release-0.3.0.json | 4 +-
en-us/docs/download/release-0.3.0.md | 94 +++++------
en-us/docs/download/release-0.5.0.html | 174 ++++++++++-----------
en-us/docs/download/release-0.5.0.json | 4 +-
en-us/docs/download/release-0.5.0.md | 174 ++++++++++-----------
en-us/docs/download/release-0.6.0.html | 46 +++---
en-us/docs/download/release-0.6.0.json | 4 +-
en-us/docs/download/release-0.6.0.md | 46 +++---
en-us/docs/download/release-0.7.0.html | 64 ++++----
en-us/docs/download/release-0.7.0.json | 4 +-
en-us/docs/download/release-0.7.0.md | 62 ++++----
en-us/docs/download/release-0.8.0.html | 160 +++++++++----------
en-us/docs/download/release-0.8.0.json | 4 +-
en-us/docs/download/release-0.8.0.md | 150 +++++++++---------
en-us/docs/error_code.html | 6 +-
en-us/docs/error_code.json | 4 +-
en-us/docs/error_code.md | 6 +-
en-us/docs/http_access_api.html | 4 +-
en-us/docs/http_access_api.json | 4 +-
en-us/docs/http_access_api.md | 4 +-
en-us/docs/producer_example.html | 4 +-
en-us/docs/producer_example.json | 4 +-
en-us/docs/producer_example.md | 4 +-
en-us/docs/quick_start.html | 84 +++++-----
en-us/docs/quick_start.json | 4 +-
en-us/docs/quick_start.md | 84 +++++-----
en-us/docs/tubemq_perf_test_vs_Kafka_cn.html | 82 +++++-----
en-us/docs/tubemq_perf_test_vs_Kafka_cn.json | 2 +-
en-us/docs/tubemq_perf_test_vs_Kafka_cn.md | 82 +++++-----
en-us/index.html | 2 +-
img/Tube logo.svg | 2 +-
zh-cn/community/index.html | 2 +-
zh-cn/docs/architecture.html | 36 ++---
zh-cn/docs/architecture.json | 4 +-
zh-cn/docs/architecture.md | 36 ++---
zh-cn/docs/client_rpc.html | 14 +-
zh-cn/docs/client_rpc.json | 4 +-
zh-cn/docs/client_rpc.md | 14 +-
zh-cn/docs/clients_java.html | 24 +--
zh-cn/docs/clients_java.json | 4 +-
zh-cn/docs/clients_java.md | 24 +--
zh-cn/docs/configure_introduction.html | 18 +--
zh-cn/docs/configure_introduction.json | 4 +-
zh-cn/docs/configure_introduction.md | 18 +--
zh-cn/docs/console_introduction.html | 24 +--
zh-cn/docs/console_introduction.json | 4 +-
zh-cn/docs/console_introduction.md | 24 +--
zh-cn/docs/consumer_example.html | 4 +-
zh-cn/docs/consumer_example.json | 4 +-
zh-cn/docs/consumer_example.md | 4 +-
zh-cn/docs/contact.html | 14 +-
zh-cn/docs/contact.json | 4 +-
zh-cn/docs/contact.md | 8 +-
zh-cn/docs/deployment.html | 26 +--
zh-cn/docs/deployment.json | 4 +-
zh-cn/docs/deployment.md | 26 +--
.../development/how-to-become-a-committer.html | 22 +--
.../development/how-to-become-a-committer.json | 4 +-
.../docs/development/how-to-become-a-committer.md | 22 +--
zh-cn/docs/development/how-to-commit.html | 46 +++---
zh-cn/docs/development/how-to-commit.json | 4 +-
zh-cn/docs/development/how-to-commit.md | 46 +++---
zh-cn/docs/development/how-to-contribute.html | 38 ++---
zh-cn/docs/development/how-to-contribute.json | 4 +-
zh-cn/docs/development/how-to-contribute.md | 38 ++---
zh-cn/docs/development/how-to-release.html | 158 +++++++++----------
zh-cn/docs/development/how-to-release.json | 4 +-
zh-cn/docs/development/how-to-release.md | 158 +++++++++----------
zh-cn/docs/development/how-to-subscribe.html | 38 ++---
zh-cn/docs/development/how-to-subscribe.json | 4 +-
zh-cn/docs/development/how-to-subscribe.md | 26 +--
zh-cn/docs/development/how-to-use-jira.html | 16 +-
zh-cn/docs/development/how-to-use-jira.json | 4 +-
zh-cn/docs/development/how-to-use-jira.md | 16 +-
zh-cn/docs/development/how-to-verify.html | 24 +--
zh-cn/docs/development/how-to-verify.json | 4 +-
zh-cn/docs/development/how-to-verify.md | 26 +--
.../development/how-to-vote-a-committer-ppmc.html | 24 +--
.../development/how-to-vote-a-committer-ppmc.json | 4 +-
.../development/how-to-vote-a-committer-ppmc.md | 24 +--
zh-cn/docs/download/download.html | 34 ++--
zh-cn/docs/download/download.json | 4 +-
zh-cn/docs/download/download.md | 34 ++--
zh-cn/docs/download/release-0.3.0.html | 94 +++++------
zh-cn/docs/download/release-0.3.0.json | 4 +-
zh-cn/docs/download/release-0.3.0.md | 94 +++++------
zh-cn/docs/download/release-0.5.0.html | 174 ++++++++++-----------
zh-cn/docs/download/release-0.5.0.json | 4 +-
zh-cn/docs/download/release-0.5.0.md | 174 ++++++++++-----------
zh-cn/docs/download/release-0.6.0.html | 46 +++---
zh-cn/docs/download/release-0.6.0.json | 4 +-
zh-cn/docs/download/release-0.6.0.md | 46 +++---
zh-cn/docs/download/release-0.7.0.html | 64 ++++----
zh-cn/docs/download/release-0.7.0.json | 4 +-
zh-cn/docs/download/release-0.7.0.md | 62 ++++----
zh-cn/docs/download/release-0.8.0.md | 150 +++++++++---------
zh-cn/docs/error_code.html | 6 +-
zh-cn/docs/error_code.json | 4 +-
zh-cn/docs/error_code.md | 6 +-
zh-cn/docs/http_access_api.html | 4 +-
zh-cn/docs/http_access_api.json | 4 +-
zh-cn/docs/http_access_api.md | 4 +-
zh-cn/docs/producer_example.html | 4 +-
zh-cn/docs/producer_example.json | 4 +-
zh-cn/docs/producer_example.md | 4 +-
zh-cn/docs/quick_start.html | 82 +++++-----
zh-cn/docs/quick_start.json | 4 +-
zh-cn/docs/quick_start.md | 82 +++++-----
zh-cn/docs/tubemq_perf_test_vs_Kafka_cn.html | 82 +++++-----
zh-cn/docs/tubemq_perf_test_vs_Kafka_cn.json | 2 +-
zh-cn/docs/tubemq_perf_test_vs_Kafka_cn.md | 82 +++++-----
zh-cn/index.html | 2 +-
220 files changed, 3753 insertions(+), 3753 deletions(-)
diff --git a/.asf.yaml b/.asf.yaml
index 9a42fb8..6b14ce5 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -8,10 +8,10 @@ publish:
whoami: asf-site
notifications:
- commits: commits@inlong.apache.org
- issues: commits@inlong.apache.org
- pullrequests_status: commits@inlong.apache.org
- pullrequests_comment: commits@inlong.apache.org
- issues_status: dev@inlong.apache.org
- issues_comment: commits@inlong.apache.org
+ commits: commits@tubemq.apache.org
+ issues: commits@tubemq.apache.org
+ pullrequests_status: commits@tubemq.apache.org
+ pullrequests_comment: commits@tubemq.apache.org
+ issues_status: dev@tubemq.apache.org
+ issues_comment: commits@tubemq.apache.org
jira_options: link label worklog
\ No newline at end of file
diff --git a/docs/en-us/architecture.md b/docs/en-us/architecture.md
index 43e48db..a0ee089 100644
--- a/docs/en-us/architecture.md
+++ b/docs/en-us/architecture.md
@@ -1,14 +1,14 @@
---
-title: Architecture - Apache inlong
+title: Architecture - Apache TubeMQ
---
-## inlong Architecture： ##
-After years of evolution, the inlong cluster is divided into the following 5 parts:
+## TubeMQ Architecture： ##
+After years of evolution, the TubeMQ cluster is divided into the following 5 parts:
- **Portal：** The Portal part responsible for external interaction and maintenance operations, including API and Web. The API connects to the management system outside the cluster. The Web is a page encapsulation of daily operation and maintenance functions based on the API;
-- **Master：** It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using inlong Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, metadata query, etc;
+- **Master：** It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using TubeMQ Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, metadata query, etc;
- **Broker：** The Store part responsible for data storage. This part is composed of independent Broker nodes. Each Broker node manages the Topic set in this node, including the addition, deletion, modification, and inquiring about Topics. It is also responsible for message storage, consumption, aging, partition expansion, data consumption offset records, etc. on the topic, and the external capabilities of the cluster, including the number of topics, throughput, and capacity, are complete [...]
@@ -17,9 +17,9 @@ After years of evolution, the inlong cluster is divided into the following 5 par
- **Zookeeper：** Responsible for the zk part of the offset storage. This part of the function has been weakened to only the persistent storage of the offset. Considering the next multi-node copy function, this module is temporarily reserved;
## Broker File Storage Scheme Improvement： ##
-Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,inlong is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, inlong has made some improvements:
+Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,TubeMQ is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, TubeMQ has made some improvements:
-1. **File structure and organization adjustment:** inlong's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
+1. **File structure and organization adjustment:** TubeMQ's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
2. **Memory block cache:** We add an additional memory cache block for each storage instance based on the file storage, i.e. add a piece of memory to the original write disk to isolate the slow impact of hard disk. The data is brushed into memory first, and the memory control block then brushes the data to disk files in bulk.
diff --git a/docs/en-us/client_rpc.md b/docs/en-us/client_rpc.md
index 43b4037..e935b4e 100644
--- a/docs/en-us/client_rpc.md
+++ b/docs/en-us/client_rpc.md
@@ -1,17 +1,17 @@
---
-title: Client RPC - Apache inlong
+title: Client RPC - Apache TubeMQ
---
-# Definition of Apache inlong RPC
+# Definition of Apache TubeMQ RPC
## General Introduction
-Implements of this part can be found in `org.apache.inlong.corerpc`. Each node in Apache inlong Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
+Implements of this part can be found in `org.apache.tubemq.corerpc`. Each node in Apache TubeMQ Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
-All we can see in TCP are binary streams. We defind a 4-byte msgToken message `RPC\_PROTOCOL\_BEGIN\_TOKEN` in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by inlong or something wrong may happended. Follows is a 4-byte serialNo, this field is sent by [...]
+All we can see in TCP are binary streams. We defind a 4-byte msgToken message `RPC\_PROTOCOL\_BEGIN\_TOKEN` in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by TubeMQ or something wrong may happended. Follows is a 4-byte serialNo, this field is sent by [...]
-We defined `listSize` as `\<len\>\<data\>` because serialized PB data is saved as a ByteBuffer object in inlong, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.
+We defined `listSize` as `\<len\>\<data\>` because serialized PB data is saved as a ByteBuffer object in TubeMQ, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.
**Pay more attention when implementing multiple languages and SDKs.** Need to serialize PB data content into arrays of blocks(supported in PB codecs).
@@ -24,7 +24,7 @@ PB format encoding is divided into RPC framework definition, to the Master messa
`RPC.proto` defines 6 struct, which divided into 2 class: Request message and Response message. Response message is divided into Successful Response and Exception Response.
-The request message encoding and response message decoding can be implemented in the `NettyClient.java` class. There is some room for improvement in this part of the definition and can be found in [inlong-109](https://issues.apache.org/jira/browse/inlong-109). However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol implementation module require [...]
+The request message encoding and response message decoding can be implemented in the `NettyClient.java` class. There is some room for improvement in this part of the definition and can be found in [TUBEMQ-109](https://issues.apache.org/jira/browse/TUBEMQ-109). However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol implementation module require [...]
Flag marks whether the message is requested or not, and the next three marks represent the content of the message trace, which is not currently used; the related is a fixed mapping of the service type, protocol version, service type, etc., the more critical parameter RequestBody.timeout is the maximum allowable time from when a request is received by the server to when it is actually processed. Long wait time, discarded if exceeded, current default is 10 seconds, request filled as follows.
@@ -56,7 +56,7 @@ Consumer has 7 pairs of command in all, Register, Heartbeat, Exit to Master; Reg
-As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because inlong is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer in [...]
+As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because TubeMQ is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer in [...]
##Client feature:
@@ -167,7 +167,7 @@ This part is related to the definition of RPC Message.
**Partition Loadbalance**:
----------
-Apache inlong currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.
+Apache TubeMQ currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.
**Server side load balancing**:
diff --git a/docs/en-us/clients_java.md b/docs/en-us/clients_java.md
index 5a6a3da..d2c5a8d 100644
--- a/docs/en-us/clients_java.md
+++ b/docs/en-us/clients_java.md
@@ -1,8 +1,8 @@
---
-title: JAVA SDK API - Apache inlong
+title: JAVA SDK API - Apache TubeMQ
---
-## **inlong Lib** **接口使用**
+## **TubeMQ Lib** **接口使用**
------
@@ -12,19 +12,19 @@ title: JAVA SDK API - Apache inlong
#### **a) MessageSessionFactory（消息会话工厂）：**
-inlong 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
+TubeMQ 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
#### **b) MasterInfo:**
-inlong的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于inlong Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于inlong的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
+TubeMQ的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于TubeMQ Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于TubeMQ的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
#### **c) TubeClientConfig：**
-MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与inlong-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前inlong的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
+MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与TubeMQ-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前TubeMQ的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
@@ -36,7 +36,7 @@ ConsumerConfig类是TubeClientConfig类的子类，它是在TubeClientConfig类
#### **e) Message：**
-Message类是inlong里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与inlong系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增inlong系统填写的内容，并在后续的版本中，新增的inlong系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做inlong进行数据收发统计时消息时间统计维度用。
+Message类是TubeMQ里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与TubeMQ系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增TubeMQ系统填写的内容，并在后续的版本中，新增的TubeMQ系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做TubeMQ进行数据收发统计时消息时间统计维度用。
@@ -48,7 +48,7 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **g) MessageConsumer：**
-该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上inlong是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
+该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上TubeMQ是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
- a. CompleteSubscribe接口，带参数的接口支持客户端对指定的分区进行指定offset消费，不带参数的接口则按照ConsumerConfig.setConsumeModel(int consumeModel)接口进行对应的消费模式设置来消费数据;
@@ -64,13 +64,13 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **a) 环境准备：**
-inlong开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的inlong集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
+TubeMQ开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的TubeMQ集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
#### **b) 创建Consumer：**
-见包org.apache.inlong.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
+见包org.apache.tubemq.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
- ###### **i.初始化MessageConsumerExample类：**
@@ -172,7 +172,7 @@ public class DefaultMessageListener implements MessageV2Listener {
#### **c) 创建Producer：**
-现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用inlong进行使用的场景，这里提供对应的使用demo，见包org.apache.inlong.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的inlong集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
+现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用TubeMQ进行使用的场景，这里提供对应的使用demo，见包org.apache.tubemq.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的TubeMQ集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
- **i. 初始化MessageProducerExample类：**
@@ -218,7 +218,7 @@ public void publishTopics(List<String> topicList) throws TubeClientException {
- **iii. 进行数据生产：**
-如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《inlong错误信息介绍.xlsx》：
+如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《TubeMQ错误信息介绍.xlsx》：
```java
public void sendMessageAsync(int id, long currtime,
@@ -248,7 +248,7 @@ public void sendMessageAsync(int id, long currtime,
- **iv. Producer不同类MAMessageProducerExample关注点：**
-该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（inlong通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
+该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（TubeMQ通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
diff --git a/docs/en-us/configure_introduction.md b/docs/en-us/configure_introduction.md
index 82d0691..3ae8962 100644
--- a/docs/en-us/configure_introduction.md
+++ b/docs/en-us/configure_introduction.md
@@ -1,12 +1,12 @@
---
-title: Configure Introduction - Apache inlong
+title: Configure Introduction - Apache TubeMQ
---
-# inlong configuration item description
+# TubeMQ configuration item description
-The inlong server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, inlong. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separately.
+The TubeMQ server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, TubeMQ. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separately.
-Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the inlong-server-3.8.0/conf/ directory.
+Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the tubemq-server-3.8.0/conf/ directory.
Their configuration is defined by a set of configuration units. The Master configuration consists of four mandatory units: [master], [zookeeper], [bdbStore], and optional [tlsSetting]. The Broker configuration is mandatory. Broker], [zookeeper] and optional [tlsSetting] consist of a total of 3 configuration units; in actual use, you can also combine the contents of the two configuration files into one ini file.
@@ -46,7 +46,7 @@ In addition to the back-end system configuration file, the Master also stores th
| startConsumeAuthenticate | no | boolean | Whether to enable consumer user authentication, the default is false |
| startConsumeAuthorize | no | boolean | Whether to enable consumer consumption authorization authentication, the default is false |
| maxGroupBrokerConsumeRate | no | int | The maximum ratio of the number of clustered brokers to the number of members in the consumer group. The default is 50. In a 50-kerrow cluster, one consumer group is allowed to start at least one client. |
-| metaDataPath | no | string | Metadata storage path. Absolute, or relative to inlong base directory (`$BASE_DIR`). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior `0.5.0`. |
+| metaDataPath | no | string | Metadata storage path. Absolute, or relative to TubeMQ base directory (`$BASE_DIR`). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior `0.5.0`. |
[zookeeper]
>The corresponding Tom MQ cluster of the Master stores the information about the ZooKeeper cluster of the Offset. The required unit has a fixed value of "[zookeeper]".
@@ -65,7 +65,7 @@ In addition to the back-end system configuration file, the Master also stores th
| Name | Required | Type | Description |
| ----------------------- | ----------------------------- | ----------------------------- | ------------------------------------------------------------ |
-| repGroupName | no | string | Cluster name, the primary and backup master node values must be the same. Optional field, default is "inlongMasterGroup". |
+| repGroupName | no | string | Cluster name, the primary and backup master node values must be the same. Optional field, default is "tubemqMasterGroup". |
| repNodeName | yes | string | The name of the master node in the cluster. The value of each node MUST BE DIFFERENT. Required field. |
| repNodePort | no | int | Node communication port, optional field, default is 9001. |
| repHelperHost | no | string | Primary node when the master cluster starts, optional field, default is "127.0.0.1:9001". |
diff --git a/docs/en-us/console_introduction.md b/docs/en-us/console_introduction.md
index 79b4c26..0ec9c20 100644
--- a/docs/en-us/console_introduction.md
+++ b/docs/en-us/console_introduction.md
@@ -1,23 +1,23 @@
---
-title: Console Introduction - Apache inlong
+title: Console Introduction - Apache TubeMQ
---
-# inlong管控台操作指引
+# TubeMQ管控台操作指引
## 管控台关系
- inlong管控台是管理inlong集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与inlong系统相关的运营数据及操作。需要说明的是，当前提供的inlong前台所提供的功能没有涵盖inlong所提供的功能范围，大家可以参照《inlong HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。inlong管控台的访问地址为http://portal:webport/config/topic_list.htm：
+ TubeMQ管控台是管理TubeMQ集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与TubeMQ系统相关的运营数据及操作。需要说明的是，当前提供的TubeMQ前台所提供的功能没有涵盖TubeMQ所提供的功能范围，大家可以参照《TubeMQ HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。TubeMQ管控台的访问地址为http://portal:webport/config/topic_list.htm：
其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。
-## inlong管控台各版面介绍
+## TubeMQ管控台各版面介绍
管控台一共3项内容：分发查询，配置管理，集群管理；配置管理又分为Broker列表，Topic列表2个部分，我们先介绍简单的分发查询和集群管理，然后再介绍复杂的配置管理。
### 分发查询
- 点分发查询，我们会看到如下的列表信息，这是当前inlong集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
+ 点分发查询，我们会看到如下的列表信息，这是当前TubeMQ集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
点击记录，可以看到选中的消费组里的消费者成员，及对应消费的Broker及Partition分区信息，如下图示：
@@ -36,22 +36,22 @@ title: Console Introduction - Apache inlong
从页面信息我们也可以看到，除了Broker的记录信息外，还有Broker在该集群里的管理信息，包括是否已上线，是否处于命令处理中，是否可读，是否可写，配置是否做了更改，是否已加载变更的配置信息。
- 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《inlong HTTP访问接口定义.xls》
+ 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《TubeMQ HTTP访问接口定义.xls》
- 所有inlong管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
+ 所有TubeMQ管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
-## inlong管控台上涉及的操作及注意事项
+## TubeMQ管控台上涉及的操作及注意事项
- 如上所说，inlong管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类inlong集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
+ 如上所说，TubeMQ管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类TubeMQ集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
- 1． **inlong集群做扩缩容增、减Broker节点时，要先在inlong管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
+ 1． **TubeMQ集群做扩缩容增、减Broker节点时，要先在TubeMQ管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
- inlong集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。inlong管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
+ TubeMQ集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。TubeMQ管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
2． **Topic元数据信息需要通过套件的业务使用界面进行新增和删除操作：**
- 如下图，业务发现自己消费的Topic在inlong管控台上没有，则需要在inlong的管控台上直接操作：
+ 如下图，业务发现自己消费的Topic在TubeMQ管控台上没有，则需要在TubeMQ的管控台上直接操作：
我们通过如上图中的Topic列表项完成Topic的新增，会弹出如下框，
diff --git a/docs/en-us/consumer_example.md b/docs/en-us/consumer_example.md
index f40e764..8cc4cc7 100644
--- a/docs/en-us/consumer_example.md
+++ b/docs/en-us/consumer_example.md
@@ -1,9 +1,9 @@
---
-title: Consumer Example - Apache inlong
+title: Consumer Example - Apache TubeMQ
---
## Consumer Example
- inlong provides two ways to consumer message, PullConsumer and PushConsumer:
+ TubeMQ provides two ways to consumer message, PullConsumer and PushConsumer:
1. PullConsumer
```java
diff --git a/docs/en-us/contact.md b/docs/en-us/contact.md
index 4fa3ac1..35b693c 100644
--- a/docs/en-us/contact.md
+++ b/docs/en-us/contact.md
@@ -1,5 +1,5 @@
---
-title: Contact Us - Apache inlong
+title: Contact Us - Apache TubeMQ
---
Contact us
@@ -9,10 +9,10 @@ Contact us
| Name | Scope | | | |
|:------------------------------------------------------------------------------|:--------------------------------|:----------------------------------------------------------------|:--------------------------------------------------------------------|:-----------------------------------------------------------------------------|
- | [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
+ | [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@tubemq.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@tubemq.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/tubemq-dev/) |
-- Home page: https://inlong.apache.org
-- Issues: https://issues.apache.org/jira/browse/inlong
+- Home page: https://tubemq.apache.org
+- Issues: https://issues.apache.org/jira/browse/TubeMQ
diff --git a/docs/en-us/deployment.md b/docs/en-us/deployment.md
index 32ac11f..2a7b257 100644
--- a/docs/en-us/deployment.md
+++ b/docs/en-us/deployment.md
@@ -1,8 +1,8 @@
---
-title: Deployment - Apache inlong
+title: Deployment - Apache TubeMQ
---
-# Compile, Deploy and Examples of inlong ：
+# Compile, Deploy and Examples of TubeMQ ：
## Compile and Package Project：
@@ -12,7 +12,7 @@ Enter the root directory of project and run:
mvn clean package -Dmaven.test.skip
```
-e.g. We put the inlong project package at `E:/`, then run the above command. Compilation is complete when all subdirectories are compiled successfully.
+e.g. We put the TubeMQ project package at `E:/`, then run the above command. Compilation is complete when all subdirectories are compiled successfully.
@@ -20,12 +20,12 @@ We can also run individual compilation in each subdirectory. Steps are the same
**Server Deployment**
-As example above, entry directory `E:\GIT\inlong\inlong-server\target`, we can see several JARs. `inlong-server-3.8.0-bin.tar.gz` is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. `inlong-server-3.8.0.jar` is a server-side processing package included in `lib` of the complete project installer. Consider to daily changes and upgrades are most made to server side, we place this jar separately so that w [...]
+As example above, entry directory `E:\GIT\TubeMQ\tubemq-server\target`, we can see several JARs. `tubemq-server-3.8.0-bin.tar.gz` is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. `tubemq-server-3.8.0.jar` is a server-side processing package included in `lib` of the complete project installer. Consider to daily changes and upgrades are most made to server side, we place this jar separately so that w [...]
-Here we have a complete package deployed onto server and we place it in `/data/inlong`
+Here we have a complete package deployed onto server and we place it in `/data/tubemq`
@@ -38,7 +38,7 @@ There are 3 roles in server package: Master, Broker and Tools. Master and Broker
| --- | --- | --- | --- | --- | --- |
| 10.224.148.145 | **Master** | 8099 | 8199 | 8080 | Metadata stored at `/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | Message stored at`/stage/msgdata` |
-| | ZK | 2181 | | | Offset stored at root directory`/inlong` |
+| | ZK | 2181 | | | Offset stored at root directory`/tubemq` |
| 100.115.158.208 | **Master** | 8099 | 8199 | 8080 | Metadata stored at `/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | Message stored at`/stage/msgdata` |
| 10.224.155.80 | Producer ||||
@@ -78,7 +78,7 @@ Visiting Master's Administrator panel([http://100.115.158.208:8080/config/topic\
**Start up Broker**：
-Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire inlong cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.
+Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire TubeMQ cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.
@@ -118,7 +118,7 @@ Check the Master Control Panel, broker has successfully registered.
Configuration of Topic is similar with Broker's, we should add metadata on Master before using them, otherwise it will report an Not Found Error during production/consumption. For example, if we try to consum a non-existent topic `test`,
```
-/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
Demo returns error message.
@@ -144,17 +144,17 @@ Topic is available after overload. We can see some status of topic has changed a
**Message Production and Consumption**：
-We pack Demo for test in package or `inlong-client-3.8.0.jar` can be used for implementing your own production and consumption.
+We pack Demo for test in package or `tubemq-client-3.8.0.jar` can be used for implementing your own production and consumption.
We run Producer Demo in below script and we can see data accepted on Broker.
```
-/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
Then we run the Consumption Demo and we can see that consumption is also working properly.
```
- /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
+ /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
```
@@ -164,5 +164,5 @@ As we can see, files relative to broker's production and consumption already exi
-Here, the compilation, deployment, system configuration, startup, production and consumption of inlong has been completed!
-If you need to get further, please refer to "inlong HTTP API" and make your appropriate configuration settings.
\ No newline at end of file
+Here, the compilation, deployment, system configuration, startup, production and consumption of TubeMQ has been completed!
+If you need to get further, please refer to "TubeMQ HTTP API" and make your appropriate configuration settings.
\ No newline at end of file
diff --git a/docs/en-us/development/how-to-become-a-committer.md b/docs/en-us/development/how-to-become-a-committer.md
index 521f704..df8bc75 100644
--- a/docs/en-us/development/how-to-become-a-committer.md
+++ b/docs/en-us/development/how-to-become-a-committer.md
@@ -1,21 +1,21 @@
---
-title: How to Become a Committer - Apache InLong
+title: How to Become a Committer - Apache TubeMQ
---
-# 如何成为Apache InLong Committer 和 PPMC
+# 如何成为Apache TubeMQ Committer 和 PPMC
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
-> Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
-Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。
+> Apache TubeMQ是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
+Apache TubeMQ Committer拥有TubeMQ代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache TubeMQ Committer。
-任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
+任何人只要对TubeMQ项目做了贡献，那你就是官方承认的TubeMQ项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，
或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。
潜在贡献清单（无特定顺序）：
- 提交自己发现的Bug、特性、改进到issue
-- 更新官方文档使项目的文档是最近的、撰写InLong的最佳实践、特性剖析的各种对用户有用的文档
+- 更新官方文档使项目的文档是最近的、撰写TubeMQ的最佳实践、特性剖析的各种对用户有用的文档
- 执行测试并报告测试结果，性能测试与其他MQ的性能对比测试等
- 发布版本时，积极参与投票
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
@@ -23,15 +23,15 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
-- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
-- 有利于InLong社区发展的任何贡献
+- 发表关于TubeMQ的演讲和博客，并将这些添加到TubeMQ的官方网站
+- 有利于TubeMQ社区发展的任何贡献
- ......
更多可以参考：[ASF官方文档](https://community.apache.org/contributors/)
并不是每个人都能完成这个清单上的所有（甚至任何）项目。如果你想用其他方式来做贡献，那就去做吧（并把它们添加到列表中）。
-愉快的举止和乐于奉献的精神是您对InLong项目产生积极影响所需要的全部。
-邀请您成为Committer是您与社区长期稳定互动的结果，是InLong社区对您的信任和认可。
+愉快的举止和乐于奉献的精神是您对TubeMQ项目产生积极影响所需要的全部。
+邀请您成为Committer是您与社区长期稳定互动的结果，是TubeMQ社区对您的信任和认可。
Committer有义务审查(Review)和合并(merge)其他人提交的PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
-当你足够活跃且对社区的贡献比较大后，就可以晋升为InLong项目的PPMC成员。
+当你足够活跃且对社区的贡献比较大后，就可以晋升为TubeMQ项目的PPMC成员。
\ No newline at end of file
diff --git a/docs/en-us/development/how-to-commit.md b/docs/en-us/development/how-to-commit.md
index 9c1fc74..89022d4 100644
--- a/docs/en-us/development/how-to-commit.md
+++ b/docs/en-us/development/how-to-commit.md
@@ -1,5 +1,5 @@
---
-title: How to Commit - Apache InLong
+title: How to Commit - Apache TubeMQ
---
# 如何提交代码
@@ -7,15 +7,15 @@ title: How to Commit - Apache InLong
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
## 0. 前言
-Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
+Apache TubeMQ使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
-- InLong代码库：https://github.com/apache/incubator-inlong
+- TubeMQ代码库：https://github.com/apache/incubator-tubemq
-- InLong官网库：https://github.com/apache/incubator-inlong-website
+- TubeMQ官网库：https://github.com/apache/incubator-tubemq-website
## 1. Fork仓库
-进入 [apache/incubator-inlong](https://github.com/apache/incubator-inlong) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
+进入 [apache/incubator-tubemq](https://github.com/apache/incubator-tubemq) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
@@ -23,22 +23,22 @@ Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文
### 2.1 将代码克隆到本地
```shell
-git clone https://github.com/<your_github_name>/incubator-inlong.git
+git clone https://github.com/<your_github_name>/incubator-tubemq.git
```
clone完成后，origin会默认指向github上的远程fork地址。
-### 2.2 将 apache/incubator-inlong 添加为本地仓库的远程分支upstream
+### 2.2 将 apache/incubator-tubemq 添加为本地仓库的远程分支upstream
```shell
-cd incubator-inlong
-git remote add upstream https://github.com/apache/incubator-inlong.git
+cd incubator-tubemq
+git remote add upstream https://github.com/apache/incubator-tubemq.git
```
### 2.3 检查远程仓库设置
```shell
git remote -v
-origin https://github.com/<your_github_name>/incubator-inlong.git (fetch)
-origin https://github.com/<your_github_name>/incubator-inlong.git(push)
-upstream https://github.com/apache/incubator-inlong.git (fetch)
-upstream https://github.com/apache/incubator-inlong.git (push)
+origin https://github.com/<your_github_name>/incubator-tubemq.git (fetch)
+origin https://github.com/<your_github_name>/incubator-tubemq.git(push)
+upstream https://github.com/apache/incubator-tubemq.git (fetch)
+upstream https://github.com/apache/incubator-tubemq.git (push)
```
此时会有两个仓库：origin(自己的仓库)和upstream（官方的仓库）
@@ -48,25 +48,25 @@ git fetch upstream
git pull upstream master
```
### 2.5 新建分支
-> 一般以issue id作为分支名，如：InLong-123
+> 一般以issue id作为分支名，如：TUBEMQ-123
```shell
-git checkout -b InLong-123
+git checkout -b TUBEMQ-123
```
-**确保分支`InLong-123`是基于官方master分支的最新代码**
+**确保分支`TUBEMQ-123`是基于官方master分支的最新代码**
分支创建完成后即可进行代码更改。
### 2.6 提交代码到远程分支
-> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[InLong-123] xxx`
+> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[TUBEMQ-123] xxx`
```shell
-git commit -a -m "[InLong-123] xxx"
-git push origin InLong-123
+git commit -a -m "[TUBEMQ-123] xxx"
+git push origin TUBEMQ-123
```
## 3. 创建PR
### 3.1 打开自己的github仓库页面
- `https://github.com/<your_github_name>/incubator-inlong`
+ `https://github.com/<your_github_name>/incubator-tubemq`
### 3.2. 切换分支
- 切换到提交的分支 `InLong-123`
+ 切换到提交的分支 `TUBEMQ-123`
### 3.3. 创建新PR
点击 `New pull request`或者`Compare & pull request`
@@ -74,7 +74,7 @@ git push origin InLong-123
需要注意以下几点：
1. PR的标题必须以issue id开头，最好与commit信息保持一致
2. 可以填写部分描述信息也可以不填
- 3. 如果点击`Create pull request`后提示代码冲突，则请将`InLong-123`分支的代码
+ 3. 如果点击`Create pull request`后提示代码冲突，则请将`TUBEMQ-123`分支的代码
与master分支同步一致后在进行提交
@@ -83,4 +83,4 @@ git push origin InLong-123
创建完PR后，所有的人都可以Review代码，可能会与您讨论一些实现的细节，可能还需要你进一步修改。
**一般该PR必须有2位以上的社区PPMC/Committer +1后，才可能正式合入官方代码库。**
-最后，恭喜您已经成为了InLong的官方贡献者了！
+最后，恭喜您已经成为了TubeMQ的官方贡献者了！
diff --git a/docs/en-us/development/how-to-contribute.md b/docs/en-us/development/how-to-contribute.md
index 4312ba6..559efd6 100644
--- a/docs/en-us/development/how-to-contribute.md
+++ b/docs/en-us/development/how-to-contribute.md
@@ -1,23 +1,23 @@
---
-title: How to Contribute - Apache InLong
+title: How to Contribute - Apache TubeMQ
---
# How to Contribute
-The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! inlong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.
+The Apache TubeMQ(incubating) community welcomes contributions from anyone with a passion for distributed systems! TubeMQ has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.
-We use a review-then-commit workflow in InLong for all contributions.
+We use a review-then-commit workflow in TubeMQ for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the InLong community on the [JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the TubeMQ community on the [JIRA](https://jira.apache.org/jira/browse/TUBEMQ) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
**For all contributions:**
1. **Code:** The you-know-what part.
-2. **Review:** Submit a pull request with your contribution to our [GitHub Repo](https://github.com/apache/incubator-inlong). Work with a committer to review and iterate on the code, if needed.
-3. **Commit:** Once at least 1 InLong committer has approved the pull request, a InLong committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).
+2. **Review:** Submit a pull request with your contribution to our [GitHub Repo](https://github.com/apache/incubator-tubemq). Work with a committer to review and iterate on the code, if needed.
+3. **Commit:** Once at least 1 TubeMQ committer has approved the pull request, a TubeMQ committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).
We look forward to working with you!
@@ -25,16 +25,16 @@ We look forward to working with you!
### Mailing list(s)
-We discuss design and implementation issues on the [dev@inlong.apache.org](mailto:dev@inlong.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@inlong.apache.org). Join by emailing [`dev-subscribe@inlong.apache.org`](mailto:dev-subscribe@inlong.apache.org).
+We discuss design and implementation issues on the [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@tubemq.apache.org). Join by emailing [`dev-subscribe@tubemq.apache.org`](mailto:dev-subscribe@tubemq.apache.org).
### JIRA
-We are using [JIRA](https://jira.apache.org/jira/browse/inlong) as the issue tracking
-and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.
+We are using [JIRA](https://jira.apache.org/jira/browse/TUBEMQ) as the issue tracking
+and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all TubeMQ related work are being tracked there.
If you do not already have an JIRA account, sign up [here](https://jira.apache.org/jira/secure/Signup!default.jspa).
-If a quick [search](https://jira.apache.org/jira/projects/inlong/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
+If a quick [search](https://jira.apache.org/jira/projects/TUBEMQ/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
@@ -42,9 +42,9 @@ For moderate or large contributions, you should not start coding or writing a de
## Design
-To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the inlong community before you start coding.
+To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the TubeMQ community before you start coding.
-We are using "inlong Improvement Proposals" for managing major changes to inlong. The list of all proposals is maintained in the inlong wiki at [this page](https://cwiki.apache.org/confluence/display/inlong/inlong+Improvement+Proposals).
+We are using "TubeMQ Improvement Proposals" for managing major changes to TubeMQ. The list of all proposals is maintained in the TubeMQ wiki at [this page](https://cwiki.apache.org/confluence/display/TUBEMQ/TubeMQ+Improvement+Proposals).
## Commit (committers only)
@@ -52,10 +52,10 @@ Once the code has been peer reviewed by a committer, the next step is for the co
Pull requests should not be merged before the review has approved from at least 1 committer.
-For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/inlong/Merging+Pull+Requests)
+For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/TUBEMQ/Merging+Pull+Requests)
## Website Contributor List
-We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of inlong. Thanks again to the following participants.
+We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of TubeMQ. Thanks again to the following participants.
- deepEvolution
- missy
- min.yang
diff --git a/docs/en-us/development/how-to-release.md b/docs/en-us/development/how-to-release.md
index 58026cc..a1b7a70 100644
--- a/docs/en-us/development/how-to-release.md
+++ b/docs/en-us/development/how-to-release.md
@@ -1,5 +1,5 @@
---
-title: How to Release - Apache inlong
+title: How to Release - Apache TubeMQ
---
# 如何发布版本
@@ -10,7 +10,7 @@ title: How to Release - Apache inlong
## 0. 前言
Source Release是Apache关注的重点，也是发布的必须内容；
-Binary Release是可选项，inlong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
+Binary Release是可选项，TubeMQ可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
请参考以下链接，找到更多关于ASF的发布指南:
@@ -125,29 +125,29 @@ http://keys.gnupg.net
> 这个步骤需要使用SVN
-DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/inlong
+Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/tubemq
#### 1.5.1 在dev分支中添加公钥到KEYS，用于发布RC版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
# 这个步骤比较慢，会把所有版本都拷贝下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-➜ ~ cd inlong-dist-dev
-➜ inlong-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ cd tubemq-dist-dev
+➜ tubemq-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
#### 1.5.2 在release分支中添加公钥到KEYS，用于发布正式版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/inlong /tmp/inlong-dist-release
-➜ ~ cd inlong-dist-release
-➜ inlong-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/tubemq /tmp/tubemq-dist-release
+➜ ~ cd tubemq-dist-release
+➜ tubemq-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
### 1.6 上传GPG公钥到Github账户
@@ -222,20 +222,20 @@ $ git config user.signingkey ${KEY_ID}
> tag创建成功后，我需要将tag源码打包成一个tar包
```shell
-mkdir /tmp/apache-inlong-${release_version}-${rc_version}
-git archive --format=tar.gz --output="/tmp/apache-inlong-${release_version}-${rc_version}/apache-inlong-${release_version}-src.tar.gz" --prefix="apache-inlong-${release_version}/" $git_tag
+mkdir /tmp/apache-tubemq-${release_version}-${rc_version}
+git archive --format=tar.gz --output="/tmp/apache-tubemq-${release_version}-${rc_version}/apache-tubemq-${release_version}-src.tar.gz" --prefix="apache-tubemq-${release_version}/" $git_tag
```
### 3.4 打包二进制包
> 编译上一步打包的源码
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version} # 进入源码目录
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version} # 进入源码目录
mvn compile clean install package -DskipTests # 编译
-cp ./inlong-client/target/apache-inlong-client-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
-cp ./inlong-server/target/apache-inlong-server-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-client/target/apache-tubemq-client-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-server/target/apache-tubemq-server-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
```
### 3.5 对源码包/二进制包进行签名/sha512
@@ -253,9 +253,9 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
## 4. 准备Apache发布
### 4.1 发布jar包到Apache Nexus仓库
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version}
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version}
mvn -DskipTests deploy -Papache-release -Dmaven.javadoc.skip=true # 开始上传
```
@@ -266,20 +266,20 @@ git push origin ${release_version}-${rc_version}
```
### 4.3 上传编译好的文件到dist
-> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-### 4.3.1 将inlong checkout到本地目录
+### 4.3.1 将TubeMQ checkout到本地目录
```shell
# 这个步骤可能会比较慢，会把所有版本都考下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
```
### 4.3.2 添加public key到KEYS文件并提交到SVN仓库
```shell
-cd /tmp/inlong-dist-dev
+cd /tmp/tubemq-dist-dev
mkdir ${release_version}-${rc_version} #创建版本目录
# 将源码包和签名包拷贝到此处
-cp /tmp/apache-inlong-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
+cp /tmp/apache-tubemq-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
svn status # 检查svn状态
svn add ${release_version}-${rc_version} # 添加到svn版本
svn status # 检查svn状态
@@ -289,62 +289,62 @@ svn commit -m 'prepare for ${release_version} ${rc_version}'# 提交至svn远程
> 请确保所有的artifact都是ok的
1. **先登录**http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库
4. 点击上方的Close按钮，这个过程会进行一系列检查
5. 检查通过以后, 在下方的Summary标签页上出现一个连接，请保存好这个链接，需要放在接下来的投票邮件当中。
-链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapacheinlong-xxxx`
+链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapachetubemq-xxxx`
WARN: 请注意点击Close可能会出现失败，请检查失败原因并处理
## 5. 进入投票
-> inlong仍旧在孵化中，需要进行两次投票，
-- inlong社区投票，发邮件至：`dev@inlong.apache.org`
+> TubeMQ仍旧在孵化中，需要进行两次投票，
+- TubeMQ社区投票，发邮件至：`dev@tubemq.apache.org`
- incubator社区投票，发邮件至：`general@incubator.apache.org`
-inlong毕业之后，只需要在inlong社区投票
+TubeMQ毕业之后，只需要在TubeMQ社区投票
-### 5.1 inlong社区投票
+### 5.1 TubeMQ社区投票
#### 5.1.1 投票模板
```html
-标题：[VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
- This is a call for vote to release Apache inlong version ${release_version}-${rc_version}.
+ This is a call for vote to release Apache TubeMQ version ${release_version}-${rc_version}.
The tag to be voted on is ${release_version}-${rc_version}:
- https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
The release tarball, signature, and checksums can be found at:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Maven artifacts are available in a staging repository at:
- https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}
+ https://repository.apache.org/content/repositories/orgapachetubemq-{staging-id}
Artifacts were signed with the {YOUR_PUB_KEY} key which can be found in:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
${release_version} includes ~ ${issue_count} bug and improvement fixes done since last versions which can be found at:
- https://github.com/apache/incubator-inlong/blob/${release_version}-${rc_version}/CHANGES.md
+ https://github.com/apache/incubator-tubemq/blob/${release_version}-${rc_version}/CHANGES.md
Please download, verify, and test.
The VOTE will remain open for at least 72 hours.
- [ ] +1 Release this package as Apache inlong ${release_version}
+ [ ] +1 Release this package as Apache TubeMQ ${release_version}
[ ] +0
[ ] -1 Do not release this package because...
- To learn more about apache inlong, please see
- http://inlong.apache.org/
+ To learn more about apache tubemq, please see
+ http://tubemq.apache.org/
Checklist for reference:
@@ -360,16 +360,16 @@ Hello Apache inlong PPMC and Community,
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Thanks,
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
#### 5.1.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
xx (+1 non-binding) votes from the PPMC,
@@ -383,7 +383,7 @@ Hello Apache inlong PPMC and Community,
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
### 5.2 incubator社区投票
@@ -391,38 +391,38 @@ Your inlong Release Manager
#### 5.2.1 投票模板
```html
-标题：[VOTE] Release Apache inlong (Incubating) ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ (Incubating) ${release_version} ${rc_version}
内容：
Hello Incubator Community,
- This is a call for a vote to release Apache inlong (Incubating) version
+ This is a call for a vote to release Apache TubeMQ (Incubating) version
${release_version} ${rc_version}
- The Apache inlong community has voted on and approved a proposal to release
- Apache inlong (Incubating) version ${release_version} ${rc_version}
+ The Apache TubeMQ community has voted on and approved a proposal to release
+ Apache TubeMQ (Incubating) version ${release_version} ${rc_version}
We now kindly request the Incubator PMC members review and vote on this
incubator release.
- inlong community vote thread:
+ TubeMQ community vote thread:
• [投票链接]
Vote result thread:
• [投票结果链接]
The release candidate:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Git tag for the release:
- • https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
Release notes:
- • https://github.com/apache/incubator-inlong/releases/tag/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/releases/tag/${release_version}-${rc_version}
The artifacts signed with PGP key [填写你个人的KEY], corresponding to [填写你个人的邮箱], that can be found in keys file:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
The vote will be open for at least 72 hours or until necessary number of votes are reached.
@@ -433,18 +433,18 @@ Hello Incubator Community,
[ ] -1 disapprove with the reason
Thanks,
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
#### 5.2.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} {rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} {rc_version}
内容：
Hi all
-Thanks for reviewing and voting for Apache inlong (Incubating) ${release_version} {rc_version}
+Thanks for reviewing and voting for Apache TubeMQ (Incubating) ${release_version} {rc_version}
release, I am happy to announce the release voting has passed with [投票结果数]
binding votes, no +0 or -1 votes. Binding votes are from IPMC
@@ -456,11 +456,11 @@ The voting thread is:
[投票链接]
Many thanks for all our mentors helping us with the release procedure, and
-all IPMC helped us to review and vote for Apache inlong (Incubating) release. I will
+all IPMC helped us to review and vote for Apache TubeMQ (Incubating) release. I will
be working on publishing the artifacts soon.
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
## 6. 正式发布
@@ -468,51 +468,51 @@ On behalf of Apache inlong (Incubating) community
### 6.1 合并release-${release_version}分支的改动到master分支
### 6.2 将源码和二进制包从svn的dev目录移动到release目录
```shell
-svn mv https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/inlong/${release_version} -m "Release ${release_version}"
+svn mv https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/tubemq/${release_version} -m "Release ${release_version}"
```
### 6.3 确认dev和release下的包是否正确
-1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/inlong/)下的`${release_version}-${rc_version}`已被删除
-2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/inlong/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/inlong/)
+1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/tubemq/)下的`${release_version}-${rc_version}`已被删除
+2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/tubemq/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/tubemq/)
```shell
-svn delete https://dist.apache.org/repos/dist/release/incubator/inlong/${last_release_version} -m "Delete ${last_release_version}"
+svn delete https://dist.apache.org/repos/dist/release/incubator/tubemq/${last_release_version} -m "Delete ${last_release_version}"
```
### 6.4 在Apache Staging仓库发布版本
> 请确保所有的artifact都是ok的
1. 登录http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库，投票邮件中指定的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库，投票邮件中指定的仓库
4. 点击上方的`Release`按钮，这个过程会进行一系列检查
**等仓库同步到其他数据源，一般需要24小时**
### 6.5 更新官网链接
-### 6.6. 发邮件到 `dev@inlong.apache.org` 和 `general@incubator.apache.org`
+### 6.6. 发邮件到 `dev@tubemq.apache.org` 和 `general@incubator.apache.org`
**请确保6.4中的仓库已发布成功，一般是在6.4后的24小时后发布邮件**
宣布release邮件模板：
```html
-标题： [ANNOUNCE] Release Apache inlong(incubating) ${release_version}
+标题： [ANNOUNCE] Release Apache TubeMQ(incubating) ${release_version}
内容：
Hi all,
-The Apache inlong(incubating) community is pleased to announce
-that Apache inlong (incubating) ${release_version} has been released!
+The Apache TubeMQ(incubating) community is pleased to announce
+that Apache TubeMQ (incubating) ${release_version} has been released!
-Apache inlong is a trillion-records-scale distributed messaging queue (MQ) system,
+Apache TubeMQ is a trillion-records-scale distributed messaging queue (MQ) system,
focuses on data transmission and storage under massive data.
Download Links: xxx
Release Notes: xxx
-Website: https://inlong.apache.org/
+Website: https://tubemq.apache.org/
-inlong Resources:
-- Issue: https://issues.apache.org/jira/projects/inlong/issues
-- Mailing list: dev@inlong.apache.org
+TubeMQ Resources:
+- Issue: https://issues.apache.org/jira/projects/TUBEMQ/issues
+- Mailing list: dev@tubemq.apache.org
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
diff --git a/docs/en-us/development/how-to-subscribe.md b/docs/en-us/development/how-to-subscribe.md
index 3d70e0b..abdb85f 100644
--- a/docs/en-us/development/how-to-subscribe.md
+++ b/docs/en-us/development/how-to-subscribe.md
@@ -1,5 +1,5 @@
---
-title: Subscribe Mailing list - Apache inlong
+title: Subscribe Mailing list - Apache TubeMQ
---
# 订阅邮件列表
@@ -8,31 +8,31 @@ title: Subscribe Mailing list - Apache inlong
## 1. 前言
邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
-订阅邮件后，你可以第一时间获取inlong社区的动态，可以与社区保持同步。
+订阅邮件后，你可以第一时间获取TubeMQ社区的动态，可以与社区保持同步。
-#### inlong项目邮件列表
+#### TubeMQ项目邮件列表
|名称|描述|订阅邮件|退订邮件|邮件归档|
|:-----|:--------|:------|:-------|:-----|
-| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@inlong.apache.org) | [退订](mailto:dev-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
-| [commits@inlong.apache.org](mailto:commits@inlong.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@inlong.apache.org) | [退订](mailto:commits-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
+| [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@tubemq.apache.org) | [退订](mailto:dev-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-dev) |
+| [commits@tubemq.apache.org](mailto:commits@tubemq.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@tubemq.apache.org) | [退订](mailto:commits-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-commits) |
## 2. 订阅邮件列表
-**以订阅dev@inlong.apache.org邮件列表为例**
+**以订阅dev@tubemq.apache.org邮件列表为例**
具体步骤如下：
- 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@inlong.apache.org`
- 2. 等待直到收到一封主题为 `confirm subscribe to dev@inlong.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
+ 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@tubemq.apache.org`
+ 2. 等待直到收到一封主题为 `confirm subscribe to dev@tubemq.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
3. 直接回复该邮件，不用修改主题和添加邮件内容。
- 4. 等待直到收到一封主题为 `WELCOME to dev@inlong.apache.org` 的邮件。
- 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@inlong.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
+ 4. 等待直到收到一封主题为 `WELCOME to dev@tubemq.apache.org` 的邮件。
+ 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@tubemq.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
## 3. 退订邮件列表
退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：
-1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@inlong.apache.org`
-2. 等待直到收到一封主题为 `confirm unsubscribe from dev@inlong.apache.org` 的邮件
+1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@tubemq.apache.org`
+2. 等待直到收到一封主题为 `confirm unsubscribe from dev@tubemq.apache.org` 的邮件
3. 直接回复该邮件，不用修改主题和添加邮件内容
-4. 等待直到收到一封主题为 `GOODBYE from dev@inlong.apache.org`的邮件
+4. 等待直到收到一封主题为 `GOODBYE from dev@tubemq.apache.org`的邮件
5. 退订成功
diff --git a/docs/en-us/development/how-to-use-jira.md b/docs/en-us/development/how-to-use-jira.md
index 952e8e4..bd09898 100644
--- a/docs/en-us/development/how-to-use-jira.md
+++ b/docs/en-us/development/how-to-use-jira.md
@@ -1,5 +1,5 @@
---
-title: How to Use JIRA - Apache inlong
+title: How to Use JIRA - Apache TubeMQ
---
# JIRA使用指南
@@ -8,17 +8,17 @@ title: How to Use JIRA - Apache inlong
## 0. 前言
JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于
-项目的管理，基于此inlong项目同样使用JIRA来进行管理项目。本文将简单介绍在inlong的开发过程中如何使用JIRA。
+项目的管理，基于此TubeMQ项目同样使用JIRA来进行管理项目。本文将简单介绍在TubeMQ的开发过程中如何使用JIRA。
## 1. 注册并登陆到JIRA
对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：
1. 登录[注册](https://issues.apache.org/jira/secure/Signup!default.jspa)页面
2. 填入个人邮箱，姓名等注册信息后即可注册。
-3. 注册成功后登录并进入inlong项目。
+3. 注册成功后登录并进入TubeMQ项目。
## 2. 查看issues
-1. 打开[inlong](https://issues.apache.org/jira/projects/inlong/issues)项目页面
-2. 可以看到inlong项目的所有issue
+1. 打开[TubeMQ](https://issues.apache.org/jira/projects/TUBEMQ/issues)项目页面
+2. 可以看到TubeMQ项目的所有issue
3. 点击右上角`View all issues and filters`即可进行过滤issue，默认过滤规则包括任务类型、任务状态、负责人及输入关键字等搜索，
也点击右侧的`More`按钮，进行更多字段的过滤筛选。
@@ -29,7 +29,7 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
- 必填项
- - Project: Apache inlong
+ - Project: Apache TubeMQ
- Issue Type: 选择issue类型，包含：Task, Bug, Feature, Improvement等
- Summary: issue标题，一句话描述该issue所要表达的问题
- Reporter: issue的提交者，即本人
@@ -43,10 +43,10 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
创建好issue后可以将issue指定给自己或者其他人或者为空。如果指定给自己，此时你就可以准备开发代码解决该问题了。
-**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@inlong.apache.org或联系inlong的PPMC申请加入inlong的contributor列表，加入后即可Assign其他issue给自己**
+**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@tubemq.apache.org或联系TubeMQ的PPMC申请加入TubeMQ的contributor列表，加入后即可Assign其他issue给自己**
## 4. 关闭issues
-当该issue被解决后，可以关闭该issue，**一般由inlong的PPMC和Committer来关闭issue**。
+当该issue被解决后，可以关闭该issue，**一般由TubeMQ的PPMC和Committer来关闭issue**。
### 4.1. 点击`Resolve Issue`按钮，一般不要点击`Close Issue`,如下图所示：
diff --git a/docs/en-us/development/how-to-verify.md b/docs/en-us/development/how-to-verify.md
index 3d856d7..e8dae4d 100644
--- a/docs/en-us/development/how-to-verify.md
+++ b/docs/en-us/development/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: How to Verify - Apache inlong
+title: How to Verify - Apache TubeMQ
---
# 验证候选版本
@@ -10,7 +10,7 @@ title: How to Verify - Apache inlong
## 1. 下载要发布的候选版本到本地环境
```shell
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
```
## 2. 验证上传的版本是否合规
> 开始验证环节，验证包含但不局限于以下内容和形式
@@ -26,7 +26,7 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
### 2.2 检查gpg签名
- 导入公钥
```shell
- curl https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS > KEYS # 下载KEYS
+ curl https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS > KEYS # 下载KEYS
gpg --import KEYS # 导入KEYS到本地
```
- 信任公钥
@@ -87,15 +87,15 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
```shell
for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
#或者
- gpg --verify apache-inlong-${release_version}-src.tar.gz.asc apache-inlong-${release_version}-src.tar.gz
+ gpg --verify apache-tubemq-${release_version}-src.tar.gz.asc apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的签名是否正确
- gpg --verify apache-inlong-server-${release_version}-bin.tar.gz.asc apache-inlong-server-${release_version}-bin.tar.gz
- gpg --verify apache-inlong-client-${release_version}-bin.tar.gz.asc apache-inlong-client-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-server-${release_version}-bin.tar.gz.asc apache-tubemq-server-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-client-${release_version}-bin.tar.gz.asc apache-tubemq-client-${release_version}-bin.tar.gz
```
- 检查结果
> 出现类似以下内容则说明签名正确，关键字：**`Good signature`**
```shell
-apache-inlong-0.3.0-incubating-src.tar.gz
+apache-tubemq-0.3.0-incubating-src.tar.gz
gpg: Signature made Sat May 30 11:45:01 2020 CST
gpg: using RSA key 9B12C2228BDFF4F4CFE849445EF3A66D57EC647A
gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
@@ -106,17 +106,17 @@ gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
```shell
for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i; done
#或者
-gpg --print-md SHA512 apache-inlong-${release_version}-src.tar.gz
+gpg --print-md SHA512 apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的sha512哈希
-gpg --print-md SHA512 apache-inlong-server-${release_version}-bin.tar.gz
-gpg --print-md SHA512 apache-inlong-client-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-server-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-client-${release_version}-bin.tar.gz
# 或者
for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
```
### 2.4. 检查源码包的文件内容
- 解压缩`apache-inlong-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
@@ -126,8 +126,8 @@ for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
- ....
### 2.5 检查二进制包(如果上传了二进制包)
- 解压缩`apache-inlong-client-${release_version}-src.tar.gz`和`
- apache-inlong-server-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-client-${release_version}-src.tar.gz`和`
+ apache-tubemq-server-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
- 能否正常部署成功
diff --git a/docs/en-us/development/how-to-vote-a-committer-ppmc.md b/docs/en-us/development/how-to-vote-a-committer-ppmc.md
index f78b9d3..84f1c4e 100644
--- a/docs/en-us/development/how-to-vote-a-committer-ppmc.md
+++ b/docs/en-us/development/how-to-vote-a-committer-ppmc.md
@@ -1,46 +1,46 @@
---
-title: How to vote a Committer or PPMC - Apache inlong
+title: How to vote a Committer or PPMC - Apache TubeMQ
---
-# 成为inlong Committer 或 PPMC 的投票过程
+# 成为TubeMQ Committer 或 PPMC 的投票过程
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
-1. inlong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在inlong的private邮件列表发起讨论；
- > [DISCUSS] YYYYY as a inlong XXXXXX
+1. TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在TubeMQ的private邮件列表发起讨论；
+ > [DISCUSS] YYYYY as a TubeMQ XXXXXX
邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；
-2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在inlong的private邮件列表发起Committer或PPMC的选举投票；
- > [VOTE] YYYYY as a inlong XXXXXX
+2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在TubeMQ的private邮件列表发起Committer或PPMC的选举投票；
+ > [VOTE] YYYYY as a TubeMQ XXXXXX
投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1票则投票失败；如果-1，需要把问题说清楚，便于大家理解和知晓
3. 投票邮件结束后，由投票发起者在投票线上总结并提醒投票结束，并发投票总结邮件；
- > [RESULTS][VOTE] YYYYY as a inlong XXXXXX
+ > [RESULTS][VOTE] YYYYY as a TubeMQ XXXXXX
4. 投票总结邮件发出后，投票发起者要给候选人发起邀请邮件，该邀请邮件需要候选人通过指定的邮箱回复接受或者拒绝；
- > [Invitation] Invitation to join Apache inlong as a XXXXXX
+ > [Invitation] Invitation to join Apache TubeMQ as a XXXXXX
- 邮件主送邀请人，抄送private@inlong.apache.org
+ 邮件主送邀请人，抄送private@tubemq.apache.org
5. 候选人接受邀请后，如果候选人没有apache邮箱帐号，投票发起者需要协助候选人按照指引创建apache帐号；
6. 如果选举的是PPMC，在候选人的Apache帐号创建完成后，投票发起者还需要向IPMC的private邮件组发送知会邮件，并等待至少72小时;
- > [NOTICE] XXXXXX for inlong PPMC
+ > [NOTICE] XXXXXX for TubeMQ PPMC
- 邮件主送private@incubator.apache.org，抄送private@inlong.apache.org，IPMC们会分析合规性，直到没有疑义。
+ 邮件主送private@incubator.apache.org，抄送private@tubemq.apache.org，IPMC们会分析合规性，直到没有疑义。
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
- 7.2 向dev@inlong.apache.org邮件组发通知邮件：
+ 7.2 向dev@tubemq.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/docs/en-us/download/download.md b/docs/en-us/download/download.md
index bd9742b..9aedbf6 100644
--- a/docs/en-us/download/download.md
+++ b/docs/en-us/download/download.md
@@ -1,44 +1,44 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
## Download links
- Use the links below to download the Apache inlong Releases, the latest release is 0.8.0.
+ Use the links below to download the Apache TubeMQ Releases, the latest release is 0.8.0.
## 0.8.0 release
- Released: March 4th, 2021
- [Release Notes](release-0.8.0.md)
- - Source: [inlong-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512)]
## 0.7.0 release
- Released: December 4th, 2020
- [Release Notes](release-0.7.0.md)
- - Source: [inlong-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)]
## 0.6.0 release
- Released: October 21th, 2020
- [Release Notes](release-0.6.0.md)
- - Source: [inlong-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)]
## 0.5.0 release
- Released: August 4th, 2020
- [Release Notes](release-0.5.0.md)
- - Source: [inlong-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)]
## 0.3.0 release
- Released: June 6th, 2020
- [Release Notes](release-0.3.0.md)
- - Source: [inlong-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)]
diff --git a/docs/en-us/download/release-0.3.0.md b/docs/en-us/download/release-0.3.0.md
index 7b200b6..9184528 100644
--- a/docs/en-us/download/release-0.3.0.md
+++ b/docs/en-us/download/release-0.3.0.md
@@ -1,65 +1,65 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| June. 6th, 2020 | 0.3.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)] |
+| June. 6th, 2020 | 0.3.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
- - [[inlong-42](https://issues.apache.org/jira/browse/inlong-42)] Add peer information about message received Major New Feature
+ - [[TUBEMQ-42](https://issues.apache.org/jira/browse/TUBEMQ-42)] Add peer information about message received Major New Feature
### Improvements
- - [[inlong-7](https://issues.apache.org/jira/browse/inlong-7)] Using StringBuilder instead of StringBuffer in BaseResult
- - [[inlong-9](https://issues.apache.org/jira/browse/inlong-9)] Remove some unnecessary code
- - [[inlong-16](https://issues.apache.org/jira/browse/inlong-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
- - [[inlong-18](https://issues.apache.org/jira/browse/inlong-18)] Correct TMaster#idGenerater to TMaster#idGenerator
- - [[inlong-19](https://issues.apache.org/jira/browse/inlong-19)] Correct parameter names to fit in camel case
- - [[inlong-20](https://issues.apache.org/jira/browse/inlong-20)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-21](https://issues.apache.org/jira/browse/inlong-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
- - [[inlong-22](https://issues.apache.org/jira/browse/inlong-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
- - [[inlong-23](https://issues.apache.org/jira/browse/inlong-23)] Improve project README content introduction
- - [[inlong-24](https://issues.apache.org/jira/browse/inlong-24)] Add NOTICE and adjust LICENSE
- - [[inlong-26](https://issues.apache.org/jira/browse/inlong-26)] correct spelling (difftime-> diffTime)
- - [[inlong-27](https://issues.apache.org/jira/browse/inlong-27)] replace StringBuffer with StringBuilder
- - [[inlong-28](https://issues.apache.org/jira/browse/inlong-28)] ignore path error
- - [[inlong-29](https://issues.apache.org/jira/browse/inlong-29)] Change the package name to org.apache.inlong.""
- - [[inlong-33](https://issues.apache.org/jira/browse/inlong-33)] refactor enum implement from annoymouse inner class
- - [[inlong-38](https://issues.apache.org/jira/browse/inlong-38)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-39](https://issues.apache.org/jira/browse/inlong-39)] Optimize the loadMessageStores() logic
- - [[inlong-40](https://issues.apache.org/jira/browse/inlong-40)] Optimize message disk store classes's logic
- - [[inlong-43](https://issues.apache.org/jira/browse/inlong-43)] Add DeletePolicy's value check
- - [[inlong-44](https://issues.apache.org/jira/browse/inlong-44)] Remove unnecessary synchronized definition of shutdown () function
- - [[inlong-49](https://issues.apache.org/jira/browse/inlong-49)] setTimeoutTime change to updTimeoutTime
- - [[inlong-50](https://issues.apache.org/jira/browse/inlong-50)] Replace fastjson to gson
+ - [[TUBEMQ-7](https://issues.apache.org/jira/browse/TUBEMQ-7)] Using StringBuilder instead of StringBuffer in BaseResult
+ - [[TUBEMQ-9](https://issues.apache.org/jira/browse/TUBEMQ-9)] Remove some unnecessary code
+ - [[TUBEMQ-16](https://issues.apache.org/jira/browse/TUBEMQ-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
+ - [[TUBEMQ-18](https://issues.apache.org/jira/browse/TUBEMQ-18)] Correct TMaster#idGenerater to TMaster#idGenerator
+ - [[TUBEMQ-19](https://issues.apache.org/jira/browse/TUBEMQ-19)] Correct parameter names to fit in camel case
+ - [[TUBEMQ-20](https://issues.apache.org/jira/browse/TUBEMQ-20)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-21](https://issues.apache.org/jira/browse/TUBEMQ-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
+ - [[TUBEMQ-22](https://issues.apache.org/jira/browse/TUBEMQ-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
+ - [[TUBEMQ-23](https://issues.apache.org/jira/browse/TUBEMQ-23)] Improve project README content introduction
+ - [[TUBEMQ-24](https://issues.apache.org/jira/browse/TUBEMQ-24)] Add NOTICE and adjust LICENSE
+ - [[TUBEMQ-26](https://issues.apache.org/jira/browse/TUBEMQ-26)] correct spelling (difftime-> diffTime)
+ - [[TUBEMQ-27](https://issues.apache.org/jira/browse/TUBEMQ-27)] replace StringBuffer with StringBuilder
+ - [[TUBEMQ-28](https://issues.apache.org/jira/browse/TUBEMQ-28)] ignore path error
+ - [[TUBEMQ-29](https://issues.apache.org/jira/browse/TUBEMQ-29)] Change the package name to org.apache.tubemq.""
+ - [[TUBEMQ-33](https://issues.apache.org/jira/browse/TUBEMQ-33)] refactor enum implement from annoymouse inner class
+ - [[TUBEMQ-38](https://issues.apache.org/jira/browse/TUBEMQ-38)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-39](https://issues.apache.org/jira/browse/TUBEMQ-39)] Optimize the loadMessageStores() logic
+ - [[TUBEMQ-40](https://issues.apache.org/jira/browse/TUBEMQ-40)] Optimize message disk store classes's logic
+ - [[TUBEMQ-43](https://issues.apache.org/jira/browse/TUBEMQ-43)] Add DeletePolicy's value check
+ - [[TUBEMQ-44](https://issues.apache.org/jira/browse/TUBEMQ-44)] Remove unnecessary synchronized definition of shutdown () function
+ - [[TUBEMQ-49](https://issues.apache.org/jira/browse/TUBEMQ-49)] setTimeoutTime change to updTimeoutTime
+ - [[TUBEMQ-50](https://issues.apache.org/jira/browse/TUBEMQ-50)] Replace fastjson to gson
### Bug Fixes
- - [[inlong-10](https://issues.apache.org/jira/browse/inlong-10)] Fix Javadoc error
- - [[inlong-14](https://issues.apache.org/jira/browse/inlong-14)] Some compilation errors
- - [[inlong-15](https://issues.apache.org/jira/browse/inlong-15)] Correct typo in http_access_API_definition.md
- - [[inlong-32](https://issues.apache.org/jira/browse/inlong-32)] File path not match with package name in inlong-client module
- - [[inlong-35](https://issues.apache.org/jira/browse/inlong-35)] check illegal package's field value
- - [[inlong-36](https://issues.apache.org/jira/browse/inlong-36)] Remove unnecessary removefirst() function printing
- - [[inlong-37](https://issues.apache.org/jira/browse/inlong-37)] Offset is set to 0 when Broker goes offline
- - [[inlong-45](https://issues.apache.org/jira/browse/inlong-45)] Check groupName with checkHostName function
- - [[inlong-48](https://issues.apache.org/jira/browse/inlong-48)] No timeout when setting consumer timeout
- - [[inlong-59](https://issues.apache.org/jira/browse/inlong-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
- - [[inlong-62](https://issues.apache.org/jira/browse/inlong-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
- - [[inlong-66](https://issues.apache.org/jira/browse/inlong-66)] TubeSingleSessionFactory shutdown bug
- - [[inlong-85](https://issues.apache.org/jira/browse/inlong-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
- - [[inlong-88](https://issues.apache.org/jira/browse/inlong-88)] Broker does not take effect after the deletePolicy value is changed
- - [[inlong-149](https://issues.apache.org/jira/browse/inlong-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-153](https://issues.apache.org/jira/browse/inlong-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-10](https://issues.apache.org/jira/browse/TUBEMQ-10)] Fix Javadoc error
+ - [[TUBEMQ-14](https://issues.apache.org/jira/browse/TUBEMQ-14)] Some compilation errors
+ - [[TUBEMQ-15](https://issues.apache.org/jira/browse/TUBEMQ-15)] Correct typo in http_access_API_definition.md
+ - [[TUBEMQ-32](https://issues.apache.org/jira/browse/TUBEMQ-32)] File path not match with package name in tubemq-client module
+ - [[TUBEMQ-35](https://issues.apache.org/jira/browse/TUBEMQ-35)] check illegal package's field value
+ - [[TUBEMQ-36](https://issues.apache.org/jira/browse/TUBEMQ-36)] Remove unnecessary removefirst() function printing
+ - [[TUBEMQ-37](https://issues.apache.org/jira/browse/TUBEMQ-37)] Offset is set to 0 when Broker goes offline
+ - [[TUBEMQ-45](https://issues.apache.org/jira/browse/TUBEMQ-45)] Check groupName with checkHostName function
+ - [[TUBEMQ-48](https://issues.apache.org/jira/browse/TUBEMQ-48)] No timeout when setting consumer timeout
+ - [[TUBEMQ-59](https://issues.apache.org/jira/browse/TUBEMQ-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
+ - [[TUBEMQ-62](https://issues.apache.org/jira/browse/TUBEMQ-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
+ - [[TUBEMQ-66](https://issues.apache.org/jira/browse/TUBEMQ-66)] TubeSingleSessionFactory shutdown bug
+ - [[TUBEMQ-85](https://issues.apache.org/jira/browse/TUBEMQ-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
+ - [[TUBEMQ-88](https://issues.apache.org/jira/browse/TUBEMQ-88)] Broker does not take effect after the deletePolicy value is changed
+ - [[TUBEMQ-149](https://issues.apache.org/jira/browse/TUBEMQ-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-153](https://issues.apache.org/jira/browse/TUBEMQ-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
diff --git a/docs/en-us/download/release-0.5.0.md b/docs/en-us/download/release-0.5.0.md
index a732263..e6c4ef1 100644
--- a/docs/en-us/download/release-0.5.0.md
+++ b/docs/en-us/download/release-0.5.0.md
@@ -1,104 +1,104 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| August. 4th, 2020 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)] |
+| August. 4th, 2020 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
- - [[inlong-122](https://issues.apache.org/jira/browse/inlong-122)] Increase JAVA version collection of SDK environment
- - [[inlong-163](https://issues.apache.org/jira/browse/inlong-163)] Flume sink for inlong
- - [[inlong-197](https://issues.apache.org/jira/browse/inlong-197)] Support inlong connector for Apache Flink
- - [[inlong-238](https://issues.apache.org/jira/browse/inlong-238)] Support inlong connector for Apache Spark Streaming
- - [[inlong-239](https://issues.apache.org/jira/browse/inlong-239)] support deployment on kubernetes
+ - [[TUBEMQ-122](https://issues.apache.org/jira/browse/TUBEMQ-122)] Increase JAVA version collection of SDK environment
+ - [[TUBEMQ-163](https://issues.apache.org/jira/browse/TUBEMQ-163)] Flume sink for TubeMQ
+ - [[TUBEMQ-197](https://issues.apache.org/jira/browse/TUBEMQ-197)] Support TubeMQ connector for Apache Flink
+ - [[TUBEMQ-238](https://issues.apache.org/jira/browse/TUBEMQ-238)] Support TubeMQ connector for Apache Spark Streaming
+ - [[TUBEMQ-239](https://issues.apache.org/jira/browse/TUBEMQ-239)] support deployment on kubernetes
### IMPROVEMENTS:
- - [[inlong-46](https://issues.apache.org/jira/browse/inlong-46)] Correct some spelling issues
- - [[inlong-53](https://issues.apache.org/jira/browse/inlong-53)] fix some typos
- - [[inlong-55](https://issues.apache.org/jira/browse/inlong-55)] fix some typos
- - [[inlong-57](https://issues.apache.org/jira/browse/inlong-57)] fix some typos
- - [[inlong-58](https://issues.apache.org/jira/browse/inlong-58)] fix some typos
- - [[inlong-60](https://issues.apache.org/jira/browse/inlong-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
- - [[inlong-61](https://issues.apache.org/jira/browse/inlong-61)] minor update & fix some typos
- - [[inlong-64](https://issues.apache.org/jira/browse/inlong-64)] minor update & fix some typos
- - [[inlong-67](https://issues.apache.org/jira/browse/inlong-67)] remove synchronized & fix some typos
- - [[inlong-71](https://issues.apache.org/jira/browse/inlong-71)] using IllegalArgumentException & fix some typos
- - [[inlong-73](https://issues.apache.org/jira/browse/inlong-73)] remove duplicate codes & some minor updates
- - [[inlong-74](https://issues.apache.org/jira/browse/inlong-74)] minor updates for DefaultBdbStoreService
- - [[inlong-75](https://issues.apache.org/jira/browse/inlong-75)] remove unused Logger
- - [[inlong-76](https://issues.apache.org/jira/browse/inlong-76)] rename the classes
- - [[inlong-77](https://issues.apache.org/jira/browse/inlong-77)] fix typo
- - [[inlong-79](https://issues.apache.org/jira/browse/inlong-79)] fix typo
- - [[inlong-80](https://issues.apache.org/jira/browse/inlong-80)] Fix some typos
- - [[inlong-82](https://issues.apache.org/jira/browse/inlong-82)] Fix some typos & update comments
- - [[inlong-83](https://issues.apache.org/jira/browse/inlong-83)] Fix some typos
- - [[inlong-87](https://issues.apache.org/jira/browse/inlong-87)] Minor updates
- - [[inlong-89](https://issues.apache.org/jira/browse/inlong-89)] Minor updates
- - [[inlong-90](https://issues.apache.org/jira/browse/inlong-90)] Remove unused codes in TubeBroker
- - [[inlong-91](https://issues.apache.org/jira/browse/inlong-91)] replace explicit type with <>
- - [[inlong-93](https://issues.apache.org/jira/browse/inlong-93)] Substitute the parameterized type for client module & missed server module
- - [[inlong-94](https://issues.apache.org/jira/browse/inlong-94)] Substitute the parameterized type for core module
- - [[inlong-95](https://issues.apache.org/jira/browse/inlong-95)] Substitute the parameterized type for server module
- - [[inlong-96](https://issues.apache.org/jira/browse/inlong-96)] Fix typo & use IllegalArgumentException
- - [[inlong-98](https://issues.apache.org/jira/browse/inlong-98)] Fix typo & Simplify 'instanceof' judgment
- - [[inlong-100](https://issues.apache.org/jira/browse/inlong-100)] Fix typos & remove unused codes
- - [[inlong-101](https://issues.apache.org/jira/browse/inlong-101)] Optimize code & Fix type
- - [[inlong-103](https://issues.apache.org/jira/browse/inlong-103)] Substitute Chinese comments with English
- - [[inlong-108](https://issues.apache.org/jira/browse/inlong-108)] About maven jdk version configuration problem
- - [[inlong-127](https://issues.apache.org/jira/browse/inlong-127)] Fixed a bug & minor changes
- - [[inlong-128](https://issues.apache.org/jira/browse/inlong-128)] Shorten the log clearup check cycle
- - [[inlong-138](https://issues.apache.org/jira/browse/inlong-138)] Optimize core module test case code
- - [[inlong-141](https://issues.apache.org/jira/browse/inlong-141)] Remove the requirement to provide localHostIP
- - [[inlong-152](https://issues.apache.org/jira/browse/inlong-152)] Modify the master.ini file's annotations
- - [[inlong-154](https://issues.apache.org/jira/browse/inlong-154)] Modify the wrong comment & Minor changes for example module
- - [[inlong-155](https://issues.apache.org/jira/browse/inlong-155)] Use enum class for consume position
- - [[inlong-156](https://issues.apache.org/jira/browse/inlong-156)] Update for README.md
- - [[inlong-166](https://issues.apache.org/jira/browse/inlong-166)] Hide `bdbStore` configs in master.ini
- - [[inlong-167](https://issues.apache.org/jira/browse/inlong-167)] Change to relative paths in default configs
- - [[inlong-168](https://issues.apache.org/jira/browse/inlong-168)] Example module: remove localhost IP configuration parameters
- - [[inlong-170](https://issues.apache.org/jira/browse/inlong-170)] improve build/deployment/configuration for quick start
- - [[inlong-196](https://issues.apache.org/jira/browse/inlong-196)] use log to print exception
- - [[inlong-201](https://issues.apache.org/jira/browse/inlong-201)] [Website] Adjust user guide & fix demo example
- - [[inlong-202](https://issues.apache.org/jira/browse/inlong-202)] Add protobuf protocol syntax declaration
- - [[inlong-213](https://issues.apache.org/jira/browse/inlong-213)] Optimize code & Minor changes
- - [[inlong-216](https://issues.apache.org/jira/browse/inlong-216)] use ThreadUtil.sleep replace Thread.sleep
- - [[inlong-222](https://issues.apache.org/jira/browse/inlong-222)] Optimize code: Unnecessary boxing/unboxing conversion
- - [[inlong-224](https://issues.apache.org/jira/browse/inlong-224)] Fixed: Unnecessary conversion to string inspection for server module
- - [[inlong-226](https://issues.apache.org/jira/browse/inlong-226)] Add Windows startup scripts
- - [[inlong-227](https://issues.apache.org/jira/browse/inlong-227)] remove build guide in docker-build readme
- - [[inlong-232](https://issues.apache.org/jira/browse/inlong-232)] TubeBroker#register2Master, reconnect and wait
- - [[inlong-234](https://issues.apache.org/jira/browse/inlong-234)] Add .asf.yaml to change notifications
- - [[inlong-235](https://issues.apache.org/jira/browse/inlong-235)] Add code coverage supporting for pull request created.
- - [[inlong-237](https://issues.apache.org/jira/browse/inlong-237)] add maven module build for docker image
+ - [[TUBEMQ-46](https://issues.apache.org/jira/browse/TUBEMQ-46)] Correct some spelling issues
+ - [[TUBEMQ-53](https://issues.apache.org/jira/browse/TUBEMQ-53)] fix some typos
+ - [[TUBEMQ-55](https://issues.apache.org/jira/browse/TUBEMQ-55)] fix some typos
+ - [[TUBEMQ-57](https://issues.apache.org/jira/browse/TUBEMQ-57)] fix some typos
+ - [[TUBEMQ-58](https://issues.apache.org/jira/browse/TUBEMQ-58)] fix some typos
+ - [[TUBEMQ-60](https://issues.apache.org/jira/browse/TUBEMQ-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
+ - [[TUBEMQ-61](https://issues.apache.org/jira/browse/TUBEMQ-61)] minor update & fix some typos
+ - [[TUBEMQ-64](https://issues.apache.org/jira/browse/TUBEMQ-64)] minor update & fix some typos
+ - [[TUBEMQ-67](https://issues.apache.org/jira/browse/TUBEMQ-67)] remove synchronized & fix some typos
+ - [[TUBEMQ-71](https://issues.apache.org/jira/browse/TUBEMQ-71)] using IllegalArgumentException & fix some typos
+ - [[TUBEMQ-73](https://issues.apache.org/jira/browse/TUBEMQ-73)] remove duplicate codes & some minor updates
+ - [[TUBEMQ-74](https://issues.apache.org/jira/browse/TUBEMQ-74)] minor updates for DefaultBdbStoreService
+ - [[TUBEMQ-75](https://issues.apache.org/jira/browse/TUBEMQ-75)] remove unused Logger
+ - [[TUBEMQ-76](https://issues.apache.org/jira/browse/TUBEMQ-76)] rename the classes
+ - [[TUBEMQ-77](https://issues.apache.org/jira/browse/TUBEMQ-77)] fix typo
+ - [[TUBEMQ-79](https://issues.apache.org/jira/browse/TUBEMQ-79)] fix typo
+ - [[TUBEMQ-80](https://issues.apache.org/jira/browse/TUBEMQ-80)] Fix some typos
+ - [[TUBEMQ-82](https://issues.apache.org/jira/browse/TUBEMQ-82)] Fix some typos & update comments
+ - [[TUBEMQ-83](https://issues.apache.org/jira/browse/TUBEMQ-83)] Fix some typos
+ - [[TUBEMQ-87](https://issues.apache.org/jira/browse/TUBEMQ-87)] Minor updates
+ - [[TUBEMQ-89](https://issues.apache.org/jira/browse/TUBEMQ-89)] Minor updates
+ - [[TUBEMQ-90](https://issues.apache.org/jira/browse/TUBEMQ-90)] Remove unused codes in TubeBroker
+ - [[TUBEMQ-91](https://issues.apache.org/jira/browse/TUBEMQ-91)] replace explicit type with <>
+ - [[TUBEMQ-93](https://issues.apache.org/jira/browse/TUBEMQ-93)] Substitute the parameterized type for client module & missed server module
+ - [[TUBEMQ-94](https://issues.apache.org/jira/browse/TUBEMQ-94)] Substitute the parameterized type for core module
+ - [[TUBEMQ-95](https://issues.apache.org/jira/browse/TUBEMQ-95)] Substitute the parameterized type for server module
+ - [[TUBEMQ-96](https://issues.apache.org/jira/browse/TUBEMQ-96)] Fix typo & use IllegalArgumentException
+ - [[TUBEMQ-98](https://issues.apache.org/jira/browse/TUBEMQ-98)] Fix typo & Simplify 'instanceof' judgment
+ - [[TUBEMQ-100](https://issues.apache.org/jira/browse/TUBEMQ-100)] Fix typos & remove unused codes
+ - [[TUBEMQ-101](https://issues.apache.org/jira/browse/TUBEMQ-101)] Optimize code & Fix type
+ - [[TUBEMQ-103](https://issues.apache.org/jira/browse/TUBEMQ-103)] Substitute Chinese comments with English
+ - [[TUBEMQ-108](https://issues.apache.org/jira/browse/TUBEMQ-108)] About maven jdk version configuration problem
+ - [[TUBEMQ-127](https://issues.apache.org/jira/browse/TUBEMQ-127)] Fixed a bug & minor changes
+ - [[TUBEMQ-128](https://issues.apache.org/jira/browse/TUBEMQ-128)] Shorten the log clearup check cycle
+ - [[TUBEMQ-138](https://issues.apache.org/jira/browse/TUBEMQ-138)] Optimize core module test case code
+ - [[TUBEMQ-141](https://issues.apache.org/jira/browse/TUBEMQ-141)] Remove the requirement to provide localHostIP
+ - [[TUBEMQ-152](https://issues.apache.org/jira/browse/TUBEMQ-152)] Modify the master.ini file's annotations
+ - [[TUBEMQ-154](https://issues.apache.org/jira/browse/TUBEMQ-154)] Modify the wrong comment & Minor changes for example module
+ - [[TUBEMQ-155](https://issues.apache.org/jira/browse/TUBEMQ-155)] Use enum class for consume position
+ - [[TUBEMQ-156](https://issues.apache.org/jira/browse/TUBEMQ-156)] Update for README.md
+ - [[TUBEMQ-166](https://issues.apache.org/jira/browse/TUBEMQ-166)] Hide `bdbStore` configs in master.ini
+ - [[TUBEMQ-167](https://issues.apache.org/jira/browse/TUBEMQ-167)] Change to relative paths in default configs
+ - [[TUBEMQ-168](https://issues.apache.org/jira/browse/TUBEMQ-168)] Example module: remove localhost IP configuration parameters
+ - [[TUBEMQ-170](https://issues.apache.org/jira/browse/TUBEMQ-170)] improve build/deployment/configuration for quick start
+ - [[TUBEMQ-196](https://issues.apache.org/jira/browse/TUBEMQ-196)] use log to print exception
+ - [[TUBEMQ-201](https://issues.apache.org/jira/browse/TUBEMQ-201)] [Website] Adjust user guide & fix demo example
+ - [[TUBEMQ-202](https://issues.apache.org/jira/browse/TUBEMQ-202)] Add protobuf protocol syntax declaration
+ - [[TUBEMQ-213](https://issues.apache.org/jira/browse/TUBEMQ-213)] Optimize code & Minor changes
+ - [[TUBEMQ-216](https://issues.apache.org/jira/browse/TUBEMQ-216)] use ThreadUtil.sleep replace Thread.sleep
+ - [[TUBEMQ-222](https://issues.apache.org/jira/browse/TUBEMQ-222)] Optimize code: Unnecessary boxing/unboxing conversion
+ - [[TUBEMQ-224](https://issues.apache.org/jira/browse/TUBEMQ-224)] Fixed: Unnecessary conversion to string inspection for server module
+ - [[TUBEMQ-226](https://issues.apache.org/jira/browse/TUBEMQ-226)] Add Windows startup scripts
+ - [[TUBEMQ-227](https://issues.apache.org/jira/browse/TUBEMQ-227)] remove build guide in docker-build readme
+ - [[TUBEMQ-232](https://issues.apache.org/jira/browse/TUBEMQ-232)] TubeBroker#register2Master, reconnect and wait
+ - [[TUBEMQ-234](https://issues.apache.org/jira/browse/TUBEMQ-234)] Add .asf.yaml to change notifications
+ - [[TUBEMQ-235](https://issues.apache.org/jira/browse/TUBEMQ-235)] Add code coverage supporting for pull request created.
+ - [[TUBEMQ-237](https://issues.apache.org/jira/browse/TUBEMQ-237)] add maven module build for docker image
### BUG FIXES:
- - [[inlong-47](https://issues.apache.org/jira/browse/inlong-47)] Fix some typos
- - [[inlong-102](https://issues.apache.org/jira/browse/inlong-102)] Fix question [inlong-101] [Optimize code]
- - [[inlong-121](https://issues.apache.org/jira/browse/inlong-121)] Fix compilation alarm
- - [[inlong-139](https://issues.apache.org/jira/browse/inlong-139)] a bug in the equals method of the TubeClientConfig class
- - [[inlong-157](https://issues.apache.org/jira/browse/inlong-157)] Optimize Broker disk anomaly check
- - [[inlong-158](https://issues.apache.org/jira/browse/inlong-158)] nextWithAuthInfo2B status should be managed independently according to Broker
- - [[inlong-159](https://issues.apache.org/jira/browse/inlong-159)] Fix some typos
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
- - [[inlong-205](https://issues.apache.org/jira/browse/inlong-205)] Duplicate dependency of jetty in tuber-server pom file
- - [[inlong-206](https://issues.apache.org/jira/browse/inlong-206)] There are some residual files after executed unit tests
- - [[inlong-210](https://issues.apache.org/jira/browse/inlong-210)] Add log4j properties file for unit tests
- - [[inlong-217](https://issues.apache.org/jira/browse/inlong-217)] UPdate the je download path
- - [[inlong-218](https://issues.apache.org/jira/browse/inlong-218)] build failed: Too many files with unapproved license
- - [[inlong-230](https://issues.apache.org/jira/browse/inlong-230)] inlong run mvn test failed with openjdk version 13.0.2
- - [[inlong-236](https://issues.apache.org/jira/browse/inlong-236)] Can't get dependencies from the maven repository
- - [[inlong-253](https://issues.apache.org/jira/browse/inlong-253)] tube-consumer fetch-worker cpu used too high
- - [[inlong-254](https://issues.apache.org/jira/browse/inlong-254)] support using different mapping port for standalone mode
- - [[inlong-265](https://issues.apache.org/jira/browse/inlong-265)] Unexpected broker disappearance in broker list after updating default broker metadata
+ - [[TUBEMQ-47](https://issues.apache.org/jira/browse/TUBEMQ-47)] Fix some typos
+ - [[TUBEMQ-102](https://issues.apache.org/jira/browse/TUBEMQ-102)] Fix question [TUBEMQ-101] [Optimize code]
+ - [[TUBEMQ-121](https://issues.apache.org/jira/browse/TUBEMQ-121)] Fix compilation alarm
+ - [[TUBEMQ-139](https://issues.apache.org/jira/browse/TUBEMQ-139)] a bug in the equals method of the TubeClientConfig class
+ - [[TUBEMQ-157](https://issues.apache.org/jira/browse/TUBEMQ-157)] Optimize Broker disk anomaly check
+ - [[TUBEMQ-158](https://issues.apache.org/jira/browse/TUBEMQ-158)] nextWithAuthInfo2B status should be managed independently according to Broker
+ - [[TUBEMQ-159](https://issues.apache.org/jira/browse/TUBEMQ-159)] Fix some typos
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-205](https://issues.apache.org/jira/browse/TUBEMQ-205)] Duplicate dependency of jetty in tuber-server pom file
+ - [[TUBEMQ-206](https://issues.apache.org/jira/browse/TUBEMQ-206)] There are some residual files after executed unit tests
+ - [[TUBEMQ-210](https://issues.apache.org/jira/browse/TUBEMQ-210)] Add log4j properties file for unit tests
+ - [[TUBEMQ-217](https://issues.apache.org/jira/browse/TUBEMQ-217)] UPdate the je download path
+ - [[TUBEMQ-218](https://issues.apache.org/jira/browse/TUBEMQ-218)] build failed: Too many files with unapproved license
+ - [[TUBEMQ-230](https://issues.apache.org/jira/browse/TUBEMQ-230)] TubeMQ run mvn test failed with openjdk version 13.0.2
+ - [[TUBEMQ-236](https://issues.apache.org/jira/browse/TUBEMQ-236)] Can't get dependencies from the maven repository
+ - [[TUBEMQ-253](https://issues.apache.org/jira/browse/TUBEMQ-253)] tube-consumer fetch-worker cpu used too high
+ - [[TUBEMQ-254](https://issues.apache.org/jira/browse/TUBEMQ-254)] support using different mapping port for standalone mode
+ - [[TUBEMQ-265](https://issues.apache.org/jira/browse/TUBEMQ-265)] Unexpected broker disappearance in broker list after updating default broker metadata
\ No newline at end of file
diff --git a/docs/en-us/download/release-0.6.0.md b/docs/en-us/download/release-0.6.0.md
index 77efdf4..e171aa7 100644
--- a/docs/en-us/download/release-0.6.0.md
+++ b/docs/en-us/download/release-0.6.0.md
@@ -1,39 +1,39 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| October. 21th, 2020 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)] |
+| October. 21th, 2020 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
-- [[inlong-319](https://issues.apache.org/jira/browse/inlong-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
-- [[inlong-3](https://issues.apache.org/jira/browse/inlong-3)] C++ SDK support in inlong
+- [[TUBEMQ-319](https://issues.apache.org/jira/browse/TUBEMQ-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
+- [[TUBEMQ-3](https://issues.apache.org/jira/browse/TUBEMQ-3)] C++ SDK support in TubeMQ
### IMPROVEMENTS
-- [[inlong-311](https://issues.apache.org/jira/browse/inlong-311)] Feedback more production information
-- [[inlong-312](https://issues.apache.org/jira/browse/inlong-312)] Feedback more consumption information
-- [[inlong-325](https://issues.apache.org/jira/browse/inlong-325)] Add 406 ~ 408 error code to pullSelect call
-- [[inlong-345](https://issues.apache.org/jira/browse/inlong-345)] Optimize the call logic of getMessage() in Pull mode
-- [[inlong-352](https://issues.apache.org/jira/browse/inlong-352)] Set the parameters of the example at startup
-- [[inlong-353](https://issues.apache.org/jira/browse/inlong-353)] Update LICENSE about C/C++ SDK's code reference
-- [[inlong-356](https://issues.apache.org/jira/browse/inlong-356)] C++ SDK Codec decode add requestid
-- [[inlong-327](https://issues.apache.org/jira/browse/inlong-327)] Fix the concurrency problem in the example
+- [[TUBEMQ-311](https://issues.apache.org/jira/browse/TUBEMQ-311)] Feedback more production information
+- [[TUBEMQ-312](https://issues.apache.org/jira/browse/TUBEMQ-312)] Feedback more consumption information
+- [[TUBEMQ-325](https://issues.apache.org/jira/browse/TUBEMQ-325)] Add 406 ~ 408 error code to pullSelect call
+- [[TUBEMQ-345](https://issues.apache.org/jira/browse/TUBEMQ-345)] Optimize the call logic of getMessage() in Pull mode
+- [[TUBEMQ-352](https://issues.apache.org/jira/browse/TUBEMQ-352)] Set the parameters of the example at startup
+- [[TUBEMQ-353](https://issues.apache.org/jira/browse/TUBEMQ-353)] Update LICENSE about C/C++ SDK's code reference
+- [[TUBEMQ-356](https://issues.apache.org/jira/browse/TUBEMQ-356)] C++ SDK Codec decode add requestid
+- [[TUBEMQ-327](https://issues.apache.org/jira/browse/TUBEMQ-327)] Fix the concurrency problem in the example
### BUG FIXES
-- [[inlong-316](https://issues.apache.org/jira/browse/inlong-316)] Where the port the port is aleady used, the process throw the exception, but not exit
-- [[inlong-317](https://issues.apache.org/jira/browse/inlong-317)] The Store Manager throws java.lang.NullPointerException
-- [[inlong-320](https://issues.apache.org/jira/browse/inlong-320)] Request for static web contents would get responses with no content
-- [[inlong-354](https://issues.apache.org/jira/browse/inlong-354)] Found a dns translate bug in C/C++ sdk
-- [[inlong-306](https://issues.apache.org/jira/browse/inlong-306)] Raise Nullpointer Exception when create inlong instance
-- [[inlong-359](https://issues.apache.org/jira/browse/inlong-359)] inlong consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
+- [[TUBEMQ-316](https://issues.apache.org/jira/browse/TUBEMQ-316)] Where the port the port is aleady used, the process throw the exception, but not exit
+- [[TUBEMQ-317](https://issues.apache.org/jira/browse/TUBEMQ-317)] The Store Manager throws java.lang.NullPointerException
+- [[TUBEMQ-320](https://issues.apache.org/jira/browse/TUBEMQ-320)] Request for static web contents would get responses with no content
+- [[TUBEMQ-354](https://issues.apache.org/jira/browse/TUBEMQ-354)] Found a dns translate bug in C/C++ sdk
+- [[TUBEMQ-306](https://issues.apache.org/jira/browse/TUBEMQ-306)] Raise Nullpointer Exception when create tubemq instance
+- [[TUBEMQ-359](https://issues.apache.org/jira/browse/TUBEMQ-359)] TubeMQ consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
diff --git a/docs/en-us/download/release-0.7.0.md b/docs/en-us/download/release-0.7.0.md
index 84a654d..06d8c66 100644
--- a/docs/en-us/download/release-0.7.0.md
+++ b/docs/en-us/download/release-0.7.0.md
@@ -1,17 +1,17 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| December. 4th, 2020 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)] |
+| December. 4th, 2020 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
@@ -20,37 +20,37 @@ Use the links below to download the Apache inlong from one of our mirrors.
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-162](https://issues.apache.org/jira/browse/inlong-162) | Python SDK support in inlong | High |
-| [inlong-336](https://issues.apache.org/jira/browse/inlong-336) | Propose web portal to manage tube cluster Phase-I | Major |
-| [inlong-390](https://issues.apache.org/jira/browse/inlong-390) | support build C++ SDK with docker image | Normal |
+| [TUBEMQ-162](https://issues.apache.org/jira/browse/TUBEMQ-162) | Python SDK support in TubeMQ | High |
+| [TUBEMQ-336](https://issues.apache.org/jira/browse/TUBEMQ-336) | Propose web portal to manage tube cluster Phase-I | Major |
+| [TUBEMQ-390](https://issues.apache.org/jira/browse/TUBEMQ-390) | support build C++ SDK with docker image | Normal |
### IMPROVEMENTS:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-369](https://issues.apache.org/jira/browse/inlong-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
-| [inlong-373](https://issues.apache.org/jira/browse/inlong-373) | Reduce the redundant code of Utils::Split functions | Major |
-| [inlong-374](https://issues.apache.org/jira/browse/inlong-374) | Adjust some coding style issues | Major |
-| [inlong-375](https://issues.apache.org/jira/browse/inlong-375) | Add a section to the README file about how to compile the project| Major |
-| [inlong-385](https://issues.apache.org/jira/browse/inlong-385) | update docker images | Major |
-| [inlong-393](https://issues.apache.org/jira/browse/inlong-393) | Optimize the mapping code of WEB API | Major |
-| [inlong-406](https://issues.apache.org/jira/browse/inlong-406) | test_consumer.py works for both Python 2 and 3 | Minor |
-| [inlong-410](https://issues.apache.org/jira/browse/inlong-410) | install python package and simplify test_consumer.py | Major |
-| [inlong-416](https://issues.apache.org/jira/browse/inlong-416) | support consume from specified position | Major |
-| [inlong-417](https://issues.apache.org/jira/browse/inlong-417) | C++ Client support parse message from binary data for Python SDK | Major |
-| [inlong-419](https://issues.apache.org/jira/browse/inlong-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
+| [TUBEMQ-369](https://issues.apache.org/jira/browse/TUBEMQ-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
+| [TUBEMQ-373](https://issues.apache.org/jira/browse/TUBEMQ-373) | Reduce the redundant code of Utils::Split functions | Major |
+| [TUBEMQ-374](https://issues.apache.org/jira/browse/TUBEMQ-374) | Adjust some coding style issues | Major |
+| [TUBEMQ-375](https://issues.apache.org/jira/browse/TUBEMQ-375) | Add a section to the README file about how to compile the project| Major |
+| [TUBEMQ-385](https://issues.apache.org/jira/browse/TUBEMQ-385) | update docker images | Major |
+| [TUBEMQ-393](https://issues.apache.org/jira/browse/TUBEMQ-393) | Optimize the mapping code of WEB API | Major |
+| [TUBEMQ-406](https://issues.apache.org/jira/browse/TUBEMQ-406) | test_consumer.py works for both Python 2 and 3 | Minor |
+| [TUBEMQ-410](https://issues.apache.org/jira/browse/TUBEMQ-410) | install python package and simplify test_consumer.py | Major |
+| [TUBEMQ-416](https://issues.apache.org/jira/browse/TUBEMQ-416) | support consume from specified position | Major |
+| [TUBEMQ-417](https://issues.apache.org/jira/browse/TUBEMQ-417) | C++ Client support parse message from binary data for Python SDK | Major |
+| [TUBEMQ-419](https://issues.apache.org/jira/browse/TUBEMQ-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
### BUG FIXES:
| JIRA | Summary | Priority |
| :----------------------------------------------------------- | :----------------------------------------------------------- | :------- |
-| [inlong-365](https://issues.apache.org/jira/browse/inlong-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
-| [inlong-370](https://issues.apache.org/jira/browse/inlong-370) | Calling GetCurConsumedInfo API always returns failure | Major |
-| [inlong-376](https://issues.apache.org/jira/browse/inlong-376) | Move pullrequests_status notifications commits mail list | Major |
-| [inlong-366](https://issues.apache.org/jira/browse/inlong-366) | Found a nullpointerexception bug in broker | Normal |
-| [inlong-379](https://issues.apache.org/jira/browse/inlong-379) | Modify the memory cache size default to 3M | Normal |
-| [inlong-380](https://issues.apache.org/jira/browse/inlong-380) | Cpp client link error when gcc optimization is disabled | Major |
-| [inlong-405](https://issues.apache.org/jira/browse/inlong-405) | python sdk install files lack of the whole cpp configuration | Major |
-| [inlong-401](https://issues.apache.org/jira/browse/inlong-401) | python sdk readme bug | Minor |
-| [inlong-407](https://issues.apache.org/jira/browse/inlong-407) | Fix some content in README.md | Trivial |
-| [inlong-418](https://issues.apache.org/jira/browse/inlong-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
\ No newline at end of file
+| [TUBEMQ-365](https://issues.apache.org/jira/browse/TUBEMQ-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
+| [TUBEMQ-370](https://issues.apache.org/jira/browse/TUBEMQ-370) | Calling GetCurConsumedInfo API always returns failure | Major |
+| [TUBEMQ-376](https://issues.apache.org/jira/browse/TUBEMQ-376) | Move pullrequests_status notifications commits mail list | Major |
+| [TUBEMQ-366](https://issues.apache.org/jira/browse/TUBEMQ-366) | Found a nullpointerexception bug in broker | Normal |
+| [TUBEMQ-379](https://issues.apache.org/jira/browse/TUBEMQ-379) | Modify the memory cache size default to 3M | Normal |
+| [TUBEMQ-380](https://issues.apache.org/jira/browse/TUBEMQ-380) | Cpp client link error when gcc optimization is disabled | Major |
+| [TUBEMQ-405](https://issues.apache.org/jira/browse/TUBEMQ-405) | python sdk install files lack of the whole cpp configuration | Major |
+| [TUBEMQ-401](https://issues.apache.org/jira/browse/TUBEMQ-401) | python sdk readme bug | Minor |
+| [TUBEMQ-407](https://issues.apache.org/jira/browse/TUBEMQ-407) | Fix some content in README.md | Trivial |
+| [TUBEMQ-418](https://issues.apache.org/jira/browse/TUBEMQ-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
\ No newline at end of file
diff --git a/docs/en-us/download/release-0.8.0.md b/docs/en-us/download/release-0.8.0.md
index 2f00e0c..1773fed 100644
--- a/docs/en-us/download/release-0.8.0.md
+++ b/docs/en-us/download/release-0.8.0.md
@@ -1,17 +1,17 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| March. 4th, 2021 | 0.8.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512)] |
+| March. 4th, 2021 | 0.8.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
@@ -19,84 +19,84 @@ Use the links below to download the Apache inlong from one of our mirrors.
### IMPROVEMENTS:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-430](https://issues.apache.org/jira/browse/inlong-430) | Optimizing the implementation of HTTP API for broke | Major |
-| [inlong-445](https://issues.apache.org/jira/browse/inlong-445) | Adjust the status check default sleep interval of pullConsumeReadyChkSliceMs | Major |
-| [inlong-448](https://issues.apache.org/jira/browse/inlong-448) | Add Committer and PPMC operation process | Major |
-| [inlong-449](https://issues.apache.org/jira/browse/inlong-449) | Adjust Example implementation | Major |
-| [inlong-452](https://issues.apache.org/jira/browse/inlong-452) | Optimize rebalance performance | Major |
-| [inlong-467](https://issues.apache.org/jira/browse/inlong-467) | Add WEB APIs of Master and Broker | Major |
-| [inlong-489](https://issues.apache.org/jira/browse/inlong-489) | Add the maximum message length parameter setting | Major |
-| [inlong-495](https://issues.apache.org/jira/browse/inlong-495) | Code implementation adjustment based on SpotBugs check | Major |
-| [inlong-511](https://issues.apache.org/jira/browse/inlong-511) | Replace the conditional operator (?:) with mid() | Major |
-| [inlong-512](https://issues.apache.org/jira/browse/inlong-512) | Add package length control based on Topic | Major |
-| [inlong-515](https://issues.apache.org/jira/browse/inlong-515) | Add cluster Topic view web api | Major |
+| [TUBEMQ-430](https://issues.apache.org/jira/browse/TUBEMQ-430) | Optimizing the implementation of HTTP API for broke | Major |
+| [TUBEMQ-445](https://issues.apache.org/jira/browse/TUBEMQ-445) | Adjust the status check default sleep interval of pullConsumeReadyChkSliceMs | Major |
+| [TUBEMQ-448](https://issues.apache.org/jira/browse/TUBEMQ-448) | Add Committer and PPMC operation process | Major |
+| [TUBEMQ-449](https://issues.apache.org/jira/browse/TUBEMQ-449) | Adjust Example implementation | Major |
+| [TUBEMQ-452](https://issues.apache.org/jira/browse/TUBEMQ-452) | Optimize rebalance performance | Major |
+| [TUBEMQ-467](https://issues.apache.org/jira/browse/TUBEMQ-467) | Add WEB APIs of Master and Broker | Major |
+| [TUBEMQ-489](https://issues.apache.org/jira/browse/TUBEMQ-489) | Add the maximum message length parameter setting | Major |
+| [TUBEMQ-495](https://issues.apache.org/jira/browse/TUBEMQ-495) | Code implementation adjustment based on SpotBugs check | Major |
+| [TUBEMQ-511](https://issues.apache.org/jira/browse/TUBEMQ-511) | Replace the conditional operator (?:) with mid() | Major |
+| [TUBEMQ-512](https://issues.apache.org/jira/browse/TUBEMQ-512) | Add package length control based on Topic | Major |
+| [TUBEMQ-515](https://issues.apache.org/jira/browse/TUBEMQ-515) | Add cluster Topic view web api | Major |
### BUG FIXES:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-437](https://issues.apache.org/jira/browse/inlong-437) | Fix inlong table source sink factory instance creating problem | Major |
-| [inlong-441](https://issues.apache.org/jira/browse/inlong-441) | An error occurred when using the inlong class to create a sink table | Major |
-| [inlong-442](https://issues.apache.org/jira/browse/inlong-442) | Modifying the jvm parameters when the broker starts does not take effect | Major |
-| [inlong-443](https://issues.apache.org/jira/browse/inlong-443) | inlongSourceFunction class prints too many logs problem | Major |
-| [inlong-446](https://issues.apache.org/jira/browse/inlong-446) | Small bugs fix that do not affect the main logics | Major |
-| [inlong-450](https://issues.apache.org/jira/browse/inlong-450) | TubeClientException: Generate producer id failed | Major |
-| [inlong-453](https://issues.apache.org/jira/browse/inlong-453) | inlongSourceFunction class prints too many logs problem | Major |
-| [inlong-506](https://issues.apache.org/jira/browse/inlong-506) | cmakelist error | Major |
-| [inlong-510](https://issues.apache.org/jira/browse/inlong-510) | Found a bug in MessageProducerExample class | Major |
-| [inlong-518](https://issues.apache.org/jira/browse/inlong-518) | fix parameter pass error | Major |
-| [inlong-526](https://issues.apache.org/jira/browse/inlong-526) | Adjust the packaging script and version check list, remove the "-WIP" tag | Major |
-| [inlong-555](https://issues.apache.org/jira/browse/inlong-555) | short session data can only be written to a specific partition | Major |
-| [inlong-556](https://issues.apache.org/jira/browse/inlong-556) | Index value is bigger than the actual number of records | Low |
+| [TUBEMQ-437](https://issues.apache.org/jira/browse/TUBEMQ-437) | Fix tubemq table source sink factory instance creating problem | Major |
+| [TUBEMQ-441](https://issues.apache.org/jira/browse/TUBEMQ-441) | An error occurred when using the Tubemq class to create a sink table | Major |
+| [TUBEMQ-442](https://issues.apache.org/jira/browse/TUBEMQ-442) | Modifying the jvm parameters when the broker starts does not take effect | Major |
+| [TUBEMQ-443](https://issues.apache.org/jira/browse/TUBEMQ-443) | TubemqSourceFunction class prints too many logs problem | Major |
+| [TUBEMQ-446](https://issues.apache.org/jira/browse/TUBEMQ-446) | Small bugs fix that do not affect the main logics | Major |
+| [TUBEMQ-450](https://issues.apache.org/jira/browse/TUBEMQ-450) | TubeClientException: Generate producer id failed | Major |
+| [TUBEMQ-453](https://issues.apache.org/jira/browse/TUBEMQ-453) | TubemqSourceFunction class prints too many logs problem | Major |
+| [TUBEMQ-506](https://issues.apache.org/jira/browse/TUBEMQ-506) | cmakelist error | Major |
+| [TUBEMQ-510](https://issues.apache.org/jira/browse/TUBEMQ-510) | Found a bug in MessageProducerExample class | Major |
+| [TUBEMQ-518](https://issues.apache.org/jira/browse/TUBEMQ-518) | fix parameter pass error | Major |
+| [TUBEMQ-526](https://issues.apache.org/jira/browse/TUBEMQ-526) | Adjust the packaging script and version check list, remove the "-WIP" tag | Major |
+| [TUBEMQ-555](https://issues.apache.org/jira/browse/TUBEMQ-555) | short session data can only be written to a specific partition | Major |
+| [TUBEMQ-556](https://issues.apache.org/jira/browse/TUBEMQ-556) | Index value is bigger than the actual number of records | Low |
### TASK:
| JIRA | Summary | Priority |
|:---- |:---- | :--- |
-| [inlong-505](https://issues.apache.org/jira/browse/inlong-505) | Remove the "WIP" label of the DISCLAIMER file | Major |
-| [inlong-543](https://issues.apache.org/jira/browse/inlong-543) | Modify the LICENSE statement of multiple files and others | Major |
-| [inlong-557](https://issues.apache.org/jira/browse/inlong-557) | Handle the issues mentioned in the 0.8.0-RC2 review | Major |
-| [inlong-562](https://issues.apache.org/jira/browse/inlong-562) | Update project contents according to the 0.8.0-RC3 review | Major |
+| [TUBEMQ-505](https://issues.apache.org/jira/browse/TUBEMQ-505) | Remove the "WIP" label of the DISCLAIMER file | Major |
+| [TUBEMQ-543](https://issues.apache.org/jira/browse/TUBEMQ-543) | Modify the LICENSE statement of multiple files and others | Major |
+| [TUBEMQ-557](https://issues.apache.org/jira/browse/TUBEMQ-557) | Handle the issues mentioned in the 0.8.0-RC2 review | Major |
+| [TUBEMQ-562](https://issues.apache.org/jira/browse/TUBEMQ-562) | Update project contents according to the 0.8.0-RC3 review | Major |
### SUB-TASK:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-428](https://issues.apache.org/jira/browse/inlong-433) | Bumped version to 0.8.0-SNAPSHOT | Major |
-| [inlong-433](https://issues.apache.org/jira/browse/inlong-433) | add inlong perf-consumer/producer scripts | Major |
-| [inlong-434](https://issues.apache.org/jira/browse/inlong-434) | Adjust Broker API mapping | Major |
-| [inlong-435](https://issues.apache.org/jira/browse/inlong-435) | Create Web field Mapping | Major |
-| [inlong-436](https://issues.apache.org/jira/browse/inlong-436) | Adjust Broker's HTTP API implementation | Major |
-| [inlong-439](https://issues.apache.org/jira/browse/inlong-439) | Add Cli field Scheme definition | Major |
-| [inlong-440](https://issues.apache.org/jira/browse/inlong-440) | Add feature package tube-manager to zip | Major |
-| [inlong-444](https://issues.apache.org/jira/browse/inlong-444) | Add consume and produce Cli commands | Major |
-| [inlong-447](https://issues.apache.org/jira/browse/inlong-447) | Add Broker-Admin Cli | Major |
-| [inlong-451](https://issues.apache.org/jira/browse/inlong-451) | Replace ConsumeTupleInfo with Tuple2 | Major |
-| [inlong-457](https://issues.apache.org/jira/browse/inlong-457) | There is no need to return StringBuilder in Master.java | Major |
-| [inlong-463](https://issues.apache.org/jira/browse/inlong-463) | Adjust Master rebalance process implementation | Major |
-| [inlong-464](https://issues.apache.org/jira/browse/inlong-464) | Add parameter rebalanceParallel in master.ini | Major |
-| [inlong-470](https://issues.apache.org/jira/browse/inlong-470) | Add query API of TopicName and BrokerId collection | Major |
-| [inlong-471](https://issues.apache.org/jira/browse/inlong-471) | Add query API Introduction of TopicName and BrokerId collection | Major |
-| [inlong-472](https://issues.apache.org/jira/browse/inlong-472) | Adjust Broker's AbstractWebHandler class implementation | Major |
-| [inlong-475](https://issues.apache.org/jira/browse/inlong-475) | add the offset clone api of the consume group | Major |
-| [inlong-482](https://issues.apache.org/jira/browse/inlong-482) | Add offset query api | Major |
-| [inlong-484](https://issues.apache.org/jira/browse/inlong-484) | Add query API for topic publication information | Major |
-| [inlong-485](https://issues.apache.org/jira/browse/inlong-485) | Add the batch setting API of consume group offset | Major |
-| [inlong-486](https://issues.apache.org/jira/browse/inlong-486) | Add the delete API of consumer group offset | Major |
-| [inlong-494](https://issues.apache.org/jira/browse/inlong-494) | Update API interface instruction document | Major |
-| [inlong-499](https://issues.apache.org/jira/browse/inlong-499) | Add configure store | Major |
-| [inlong-500](https://issues.apache.org/jira/browse/inlong-500) | Add setting operate API | Major |
-| [inlong-501](https://issues.apache.org/jira/browse/inlong-501) | Adjust max message size check logic | Major |
-| [inlong-502](https://issues.apache.org/jira/browse/inlong-502) | Add setting API interface document | Major |
-| [inlong-504](https://issues.apache.org/jira/browse/inlong-504) | Adjust the WebMethodMapper class interfaces | Major |
-| [inlong-508](https://issues.apache.org/jira/browse/inlong-508) | Optimize Broker's PB parameter check processing logic | Major |
-| [inlong-509](https://issues.apache.org/jira/browse/inlong-509) | Adjust the packet length check when data is loaded | Major |
-| [inlong-522](https://issues.apache.org/jira/browse/inlong-522) | Add admin_query_cluster_topic_view API document | Major |
-| [inlong-544](https://issues.apache.org/jira/browse/inlong-544) | Adjust the LICENSE statement in the client.conf files of Python and C/C++ SDK | Major |
-| [inlong-546](https://issues.apache.org/jira/browse/inlong-546) | Restore the original license header of the referenced external source files | Major |
-| [inlong-547](https://issues.apache.org/jira/browse/inlong-547) | Recode the implementation of the *Startup.java classes in the Tool package | Major |
-| [inlong-548](https://issues.apache.org/jira/browse/inlong-548) | Handle the LICENSE authorization of font files in the resources | Major |
-| [inlong-549](https://issues.apache.org/jira/browse/inlong-549) | Handling the problem of compilation failure | Major |
-| [inlong-550](https://issues.apache.org/jira/browse/inlong-550) | Adjust LICENSE file content | Major |
-| [inlong-551](https://issues.apache.org/jira/browse/inlong-551) | Adjust NOTICE file content | Major |
-| [inlong-558](https://issues.apache.org/jira/browse/inlong-558) | Adjust the LICENSE of the file header | Major |
-| [inlong-559](https://issues.apache.org/jira/browse/inlong-559) | Update the LICENSE file according to the 0.8.0-RC2 review | Major |
-| [inlong-560](https://issues.apache.org/jira/browse/inlong-560) | Remove unprepared modules | Major |
+| [TUBEMQ-428](https://issues.apache.org/jira/browse/TUBEMQ-433) | Bumped version to 0.8.0-SNAPSHOT | Major |
+| [TUBEMQ-433](https://issues.apache.org/jira/browse/TUBEMQ-433) | add tubemq perf-consumer/producer scripts | Major |
+| [TUBEMQ-434](https://issues.apache.org/jira/browse/TUBEMQ-434) | Adjust Broker API mapping | Major |
+| [TUBEMQ-435](https://issues.apache.org/jira/browse/TUBEMQ-435) | Create Web field Mapping | Major |
+| [TUBEMQ-436](https://issues.apache.org/jira/browse/TUBEMQ-436) | Adjust Broker's HTTP API implementation | Major |
+| [TUBEMQ-439](https://issues.apache.org/jira/browse/TUBEMQ-439) | Add Cli field Scheme definition | Major |
+| [TUBEMQ-440](https://issues.apache.org/jira/browse/TUBEMQ-440) | Add feature package tube-manager to zip | Major |
+| [TUBEMQ-444](https://issues.apache.org/jira/browse/TUBEMQ-444) | Add consume and produce Cli commands | Major |
+| [TUBEMQ-447](https://issues.apache.org/jira/browse/TUBEMQ-447) | Add Broker-Admin Cli | Major |
+| [TUBEMQ-451](https://issues.apache.org/jira/browse/TUBEMQ-451) | Replace ConsumeTupleInfo with Tuple2 | Major |
+| [TUBEMQ-457](https://issues.apache.org/jira/browse/TUBEMQ-457) | There is no need to return StringBuilder in Master.java | Major |
+| [TUBEMQ-463](https://issues.apache.org/jira/browse/TUBEMQ-463) | Adjust Master rebalance process implementation | Major |
+| [TUBEMQ-464](https://issues.apache.org/jira/browse/TUBEMQ-464) | Add parameter rebalanceParallel in master.ini | Major |
+| [TUBEMQ-470](https://issues.apache.org/jira/browse/TUBEMQ-470) | Add query API of TopicName and BrokerId collection | Major |
+| [TUBEMQ-471](https://issues.apache.org/jira/browse/TUBEMQ-471) | Add query API Introduction of TopicName and BrokerId collection | Major |
+| [TUBEMQ-472](https://issues.apache.org/jira/browse/TUBEMQ-472) | Adjust Broker's AbstractWebHandler class implementation | Major |
+| [TUBEMQ-475](https://issues.apache.org/jira/browse/TUBEMQ-475) | add the offset clone api of the consume group | Major |
+| [TUBEMQ-482](https://issues.apache.org/jira/browse/TUBEMQ-482) | Add offset query api | Major |
+| [TUBEMQ-484](https://issues.apache.org/jira/browse/TUBEMQ-484) | Add query API for topic publication information | Major |
+| [TUBEMQ-485](https://issues.apache.org/jira/browse/TUBEMQ-485) | Add the batch setting API of consume group offset | Major |
+| [TUBEMQ-486](https://issues.apache.org/jira/browse/TUBEMQ-486) | Add the delete API of consumer group offset | Major |
+| [TUBEMQ-494](https://issues.apache.org/jira/browse/TUBEMQ-494) | Update API interface instruction document | Major |
+| [TUBEMQ-499](https://issues.apache.org/jira/browse/TUBEMQ-499) | Add configure store | Major |
+| [TUBEMQ-500](https://issues.apache.org/jira/browse/TUBEMQ-500) | Add setting operate API | Major |
+| [TUBEMQ-501](https://issues.apache.org/jira/browse/TUBEMQ-501) | Adjust max message size check logic | Major |
+| [TUBEMQ-502](https://issues.apache.org/jira/browse/TUBEMQ-502) | Add setting API interface document | Major |
+| [TUBEMQ-504](https://issues.apache.org/jira/browse/TUBEMQ-504) | Adjust the WebMethodMapper class interfaces | Major |
+| [TUBEMQ-508](https://issues.apache.org/jira/browse/TUBEMQ-508) | Optimize Broker's PB parameter check processing logic | Major |
+| [TUBEMQ-509](https://issues.apache.org/jira/browse/TUBEMQ-509) | Adjust the packet length check when data is loaded | Major |
+| [TUBEMQ-522](https://issues.apache.org/jira/browse/TUBEMQ-522) | Add admin_query_cluster_topic_view API document | Major |
+| [TUBEMQ-544](https://issues.apache.org/jira/browse/TUBEMQ-544) | Adjust the LICENSE statement in the client.conf files of Python and C/C++ SDK | Major |
+| [TUBEMQ-546](https://issues.apache.org/jira/browse/TUBEMQ-546) | Restore the original license header of the referenced external source files | Major |
+| [TUBEMQ-547](https://issues.apache.org/jira/browse/TUBEMQ-547) | Recode the implementation of the *Startup.java classes in the Tool package | Major |
+| [TUBEMQ-548](https://issues.apache.org/jira/browse/TUBEMQ-548) | Handle the LICENSE authorization of font files in the resources | Major |
+| [TUBEMQ-549](https://issues.apache.org/jira/browse/TUBEMQ-549) | Handling the problem of compilation failure | Major |
+| [TUBEMQ-550](https://issues.apache.org/jira/browse/TUBEMQ-550) | Adjust LICENSE file content | Major |
+| [TUBEMQ-551](https://issues.apache.org/jira/browse/TUBEMQ-551) | Adjust NOTICE file content | Major |
+| [TUBEMQ-558](https://issues.apache.org/jira/browse/TUBEMQ-558) | Adjust the LICENSE of the file header | Major |
+| [TUBEMQ-559](https://issues.apache.org/jira/browse/TUBEMQ-559) | Update the LICENSE file according to the 0.8.0-RC2 review | Major |
+| [TUBEMQ-560](https://issues.apache.org/jira/browse/TUBEMQ-560) | Remove unprepared modules | Major |
diff --git a/docs/en-us/error_code.md b/docs/en-us/error_code.md
index b9f2dca..4eb22dd 100644
--- a/docs/en-us/error_code.md
+++ b/docs/en-us/error_code.md
@@ -1,10 +1,10 @@
---
-title: Error Code - Apache inlong
+title: Error Code - Apache TubeMQ
---
-# Introduction of inlong Error
+# Introduction of TubeMQ Error
- inlong use `errCode` and `errMsg` combined to return specific operation result.
+ TubeMQ use `errCode` and `errMsg` combined to return specific operation result.
Firstly, determine the type of result(problem) by errCode, and then determine the specific reson of the errCode based on errMsg.
The following table summarizes all the errCodes and errMsgs that may return during operation.
diff --git a/docs/en-us/http_access_api.md b/docs/en-us/http_access_api.md
index 92b40ab..0568efa 100644
--- a/docs/en-us/http_access_api.md
+++ b/docs/en-us/http_access_api.md
@@ -1,5 +1,5 @@
---
-title: HTTP API - Apache inlong
+title: HTTP API - Apache TubeMQ
---
# HTTP access API definition
@@ -912,7 +912,7 @@ __Request__
|needRefresh|no|whether it needs to refresh, default false|Boolean|
More API see:
-<a href="appendixfiles/http_access_api_definition_cn.xls" target="_blank">inlong HTTP API</a>
+<a href="appendixfiles/http_access_api_definition_cn.xls" target="_blank">TubeMQ HTTP API</a>
---
<a href="#top">Back to top</a>
\ No newline at end of file
diff --git a/docs/en-us/producer_example.md b/docs/en-us/producer_example.md
index a70d5a5..d7c25da 100644
--- a/docs/en-us/producer_example.md
+++ b/docs/en-us/producer_example.md
@@ -1,9 +1,9 @@
---
-title: Producer Example - Apache inlong
+title: Producer Example - Apache TubeMQ
---
## Producer Example
- inlong provides two ways to initialize session factory, TubeSingleSessionFactory and TubeMultiSessionFactory:
+ TubeMQ provides two ways to initialize session factory, TubeSingleSessionFactory and TubeMultiSessionFactory:
- TubeSingleSessionFactory creates only one session in the lifecycle, this is very useful in streaming scenarios.
- TubeMultiSessionFactory creates new session on every call.
diff --git a/docs/en-us/quick_start.md b/docs/en-us/quick_start.md
index 8382d62..ad84f77 100644
--- a/docs/en-us/quick_start.md
+++ b/docs/en-us/quick_start.md
@@ -1,8 +1,8 @@
---
-title: Quick Start - Apache inlong
+title: Quick Start - Apache TubeMQ
---
-## Build inlong
+## Build TubeMQ
### Prerequisites
- Java JDK 1.7 or 1.8
- Maven 3.3+
@@ -14,7 +14,7 @@ mvn clean package -DskipTests
```
- (Optional) Build Using Docker：
```bash
-docker run -v REPLACE_WITH_SOURCE_PATH:/inlong apacheinlong/inlong-build clean package -DskipTests
+docker run -v REPLACE_WITH_SOURCE_PATH:/tubemq apachetubemq/tubemq-build clean package -DskipTests
```
- Run Unit Tests：
```bash
@@ -23,11 +23,11 @@ mvn test
- Build Individual Module：
```bash
mvn clean install
-cd module-name (e.g. inlong-client)
+cd module-name (e.g. tubemq-client)
mvn test
```
-After the build, please go to `inlong-server/target`. You can find the
-**inlong-server-[inlong-VERSION]-bin.tar.gz** file. It is the inlong deployment package, which includes
+After the build, please go to `tubemq-server/target`. You can find the
+**tubemq-server-[TUBEMQ-VERSION]-bin.tar.gz** file. It is the TubeMQ deployment package, which includes
scripts, configuration files, dependency jars and web GUI code.
### Setting Up Your IDE
@@ -39,7 +39,7 @@ mvn compile
This command will generate the Java source files from the `protoc` files, the generated files located in `target/generated-sources`.
-(Optional) If you want to use local `protoc` executable, you can change the configuration of `protobuf-maven-plugin` in `inlong-core/pom.xml` as below
+(Optional) If you want to use local `protoc` executable, you can change the configuration of `protobuf-maven-plugin` in `tubemq-core/pom.xml` as below
```xml
<configuration>
@@ -49,23 +49,23 @@ This command will generate the Java source files from the `protoc` files, the ge
```
## Deploy and Start
-### Deploy inlong Standalone
+### Deploy TubeMQ Standalone
Standalone mode starts zookeeper/master/broker services in one docker container：
```
-docker run -p 8080:8080 -p 8000:8000 -p 8123:8123 --name inlong -d apacheinlong/inlong-all:latest
+docker run -p 8080:8080 -p 8000:8000 -p 8123:8123 --name tubemq -d apachetubemq/tubemq-all:latest
```
Afater container is running, you can access ` http://127.0.0.1:8080`, and reference to next `Quick Start` chapter for experience.
**Tips**：Standalone Mode is only available for development and experience, it's not designed for production environment.
-### Deploy inlong Cluster
+### Deploy TubeMQ Cluster
#### Prerequisites
- ZooKeeper Cluster
-- [inlong-server-[inlong-VERSION]-bin.tar.gz](download/download.md) package file
+- [tubemq-server-[TUBEMQ-VERSION]-bin.tar.gz](download/download.md) package file
After you extract the package file, here's the folder structure.
```
-/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin/
+/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin/
├── bin
├── conf
├── lib
@@ -81,7 +81,7 @@ like this, and all services run on the same node. Zookeeper should be setup in y
| ---- | -------- | -------- | -------- | ------- |
| Master | 8099 | 8199 | 8080 | Meta data is stored at /stage/metadata |
| Broker | 8123 | 8124 | 8081 | Message is stored at /stage/msgdata |
-| Zookeeper | 2181 | | | Offset is stored at /inlong |
+| Zookeeper | 2181 | | | Offset is stored at /tubemq |
#### Configure Master
You can change configurations in `conf/master.ini` according to cluster information.
@@ -99,20 +99,20 @@ confModAuthToken=abc // for configuring Web Resources\API etc
- ZooKeeper Cluster
```ini
[zookeeper]
-zkNodeRoot=/inlong
+zkNodeRoot=/tubemq
zkServerAddr=localhost:2181 // multi zookeeper addresses can separate with ","
```
- Replication Strategy
```ini
[replication]
-repNodeName=inlongMasterGroupNode1 // using different name for each master node
+repNodeName=tubemqMasterGroupNode1 // using different name for each master node
repHelperHost=FIRST_MASTER_NODE_IP:9001 // helperHost is used for building HA master.
```
- Resource Path of Web
You can change configurations in `resources/velocity.properties`
```properties
-file.resource.loader.path=/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin/resources/templates
+file.resource.loader.path=/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin/resources/templates
```
- (Optional) Master High Availability
@@ -150,7 +150,7 @@ primaryPath=/stage/msgdata
- ZooKeeper Cluster
```ini
[zookeeper]
-zkNodeRoot=/inlong
+zkNodeRoot=/tubemq
zkServerAddr=localhost:2181 // multi zookeeper addresses can separate with ","
```
@@ -158,12 +158,12 @@ zkServerAddr=localhost:2181 // multi zookeeper addresses can separat
Please go to the `bin` folder and run this command to start
the master service.
```bash
-./inlong master start
+./tubemq master start
```
You should be able to access `http://your-master-ip:8080` to see the
web GUI now.
-
+
#### Configure Broker Metadata
Before we start a broker service, we need to configure it on master web GUI first.
@@ -171,7 +171,7 @@ Before we start a broker service, we need to configure it on master web GUI firs
Go to the `Broker List` page, click `Add Single Broker`, and input the new broker
information.
-
+
In this example, we only need to input broker IP and authToken:
1. broker IP: broker server ip
@@ -180,44 +180,44 @@ In this example, we only need to input broker IP and authToken:
Click the online link to activate the new added broker.
-
+
#### Start Broker
Please go to the `bin` folder and run this command to start the broker service
```bash
-./inlong broker start
+./tubemq broker start
```
Refresh the GUI broker list page, you can see that the broker now is registered.
After the sub-state of the broker changed to `idle`, we can add topics to that broker.
-
+
## Quick Start
### Add Topic
We can add or manage the cluster topics on the web GUI. To add a new topic, go to the
topic list page and click the add new topic button
-
+
Then select the brokers which you want to deploy the topics to.
-
+
We can see the publish and subscribe state of the new added topic is still grey. We need
to go to the broker list page to reload the broker configuration.
-
+
-
+
When the broker sub-state changed to idle, go to the topic list page. We can see
that the topic publish/subscribe state is active now.
-
+
-
+
Now we can use the topic to send messages.
@@ -228,36 +228,36 @@ Now we can use `demo` topic which created before to test our cluster.
Please don't forget replace `YOUR_MASTER_IP` with your server ip, and start producer.
```bash
-install_path=/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin
+install_path=/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin
java -Dlog4j.configuration=file:${install_path}/conf/tools.log4j.properties \
-Djava.net.preferIPv4Stack=true -cp ${install_path}/lib/*:${install_path}/conf/* \
-org.apache.inlong.example.MessageProducerExample \
+org.apache.tubemq.example.MessageProducerExample \
YOUR_MASTER_IP:8000 demo 100000
```
From the log, we can see the message is sent out.
```bash
-[2020-06-04 11:19:04,405] INFO Send demo 1000 message, keyCount is 252 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:04,652] INFO Send demo 2000 message, keyCount is 502 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:05,096] INFO Send demo 3000 message, keyCount is 752 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:05,181] INFO Send demo 4000 message, keyCount is 1002 (org.apache.inlong.example.MessageProducerExample)
+[2020-06-04 11:19:04,405] INFO Send demo 1000 message, keyCount is 252 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:04,652] INFO Send demo 2000 message, keyCount is 502 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:05,096] INFO Send demo 3000 message, keyCount is 752 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:05,181] INFO Send demo 4000 message, keyCount is 1002 (org.apache.tubemq.example.MessageProducerExample)
```
- Consume Messages
Please don't forget replace YOUR_MASTER_IP with your server ip, and start consumer.
```bash
-java -Xmx512m -Dlog4j.configuration=file:/opt/inlong-server/conf/tools.log4j.properties \
--Djava.net.preferIPv4Stack=true -cp /opt/inlong-server/lib/*:/opt/inlong-server/conf/* \
-org.apache.inlong.example.MessageConsumerExample \
+java -Xmx512m -Dlog4j.configuration=file:/opt/tubemq-server/conf/tools.log4j.properties \
+-Djava.net.preferIPv4Stack=true -cp /opt/tubemq-server/lib/*:/opt/tubemq-server/conf/* \
+org.apache.tubemq.example.MessageConsumerExample \
YOUR_SERVER_IP:8000 demo demoGroup 3 1 1
```
From the log, we can see the message received by the consumer.
```bash
-[2020-06-04 11:20:29,107] INFO Receive messages:270000 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,206] INFO Receive messages:272500 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,590] INFO Receive messages:275000 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,910] INFO Receive messages:277500 (org.apache.inlong.example.MsgRecvStats)
+[2020-06-04 11:20:29,107] INFO Receive messages:270000 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,206] INFO Receive messages:272500 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,590] INFO Receive messages:275000 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,910] INFO Receive messages:277500 (org.apache.tubemq.example.MsgRecvStats)
```
---
diff --git a/docs/en-us/tubemq_perf_test_vs_Kafka_cn.md b/docs/en-us/tubemq_perf_test_vs_Kafka_cn.md
index 27d131e..45916f6 100644
--- a/docs/en-us/tubemq_perf_test_vs_Kafka_cn.md
+++ b/docs/en-us/tubemq_perf_test_vs_Kafka_cn.md
@@ -1,8 +1,8 @@
-# inlong VS Kafka性能对比测试总结
+# TubeMQ VS Kafka性能对比测试总结
## 背景
-inlong是腾讯大数据自研的分布式消息中间件。其系统架构思想源于[Apache Kafka](http://kafka.apache.org/)。在实现上，则完全采取自适应的方式，结合实战做了很多优化及研发工作，如分区管理、分配机制和全新节点通讯流程，自主开发高性能的底层RPC通讯模块等。
-这些实现使得inlong在保证实时性和一致性的前提下，具有很好的健壮性及更高的吞吐能力。结合目前主流消息中间件使用情况，以Kafka为参照做性能对比测试，对比常规应用场景下两套系统性能。
+TubeMQ是腾讯大数据自研的分布式消息中间件。其系统架构思想源于[Apache Kafka](http://kafka.apache.org/)。在实现上，则完全采取自适应的方式，结合实战做了很多优化及研发工作，如分区管理、分配机制和全新节点通讯流程，自主开发高性能的底层RPC通讯模块等。
+这些实现使得TubeMQ在保证实时性和一致性的前提下，具有很好的健壮性及更高的吞吐能力。结合目前主流消息中间件使用情况，以Kafka为参照做性能对比测试，对比常规应用场景下两套系统性能。
## 测试场景方案
如下是我们根据实际应用场景设计的测试方案：
@@ -13,23 +13,23 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
角色|测试场景|要点
:---:|:---:|---
-闪电侠|场景五|快 (数据生产消费时延 inlong 10ms vs kafka 250ms )
-绿巨人|场景三，场景四|抗击打能力 (随着topic数由100,200,到500,1000逐步增大，inlong系统能力不减，吞吐量随负载的提升下降微小且能力持平 vs kafka吞吐量明显下降且不稳定；过滤消费时，inlong入出流量提升直接完胜kafka的入流量下降且吞吐量下降)
-蜘蛛侠|场景八|各个场景来去自如(不同机型下对比测试，inlong吞吐量稳定 vs Kafka在BX1机型下性能更低的问题)
-钢铁侠|场景二，场景三，场景六|自动化(系统运行中inlong可以动态实时的调整系统设置、消费行为来提升系统性能）
+闪电侠|场景五|快 (数据生产消费时延 TubeMQ 10ms vs kafka 250ms )
+绿巨人|场景三，场景四|抗击打能力 (随着topic数由100,200,到500,1000逐步增大，TubeMQ系统能力不减，吞吐量随负载的提升下降微小且能力持平 vs kafka吞吐量明显下降且不稳定；过滤消费时，TubeMQ入出流量提升直接完胜kafka的入流量下降且吞吐量下降)
+蜘蛛侠|场景八|各个场景来去自如(不同机型下对比测试，TubeMQ吞吐量稳定 vs Kafka在BX1机型下性能更低的问题)
+钢铁侠|场景二，场景三，场景六|自动化(系统运行中TubeMQ可以动态实时的调整系统设置、消费行为来提升系统性能）
具体的数据分析来看：
-1. 单Topic单实例配置下，inlong吞吐量要远低于Kafka；单Topic多实例配置下，inlong在4个实例时吞吐量追上Kafka对应5个分区配置，同时inlong的吞吐量随实例数增加而增加，Kafka出现不升反降的情况；inlong可以在系统运行中通过调整各项参数来动态的控制吞吐量的提升；
-2. 多Topic多实例配置下，inlong吞吐量维持在一个非常稳定的范围，且资源消耗，包括文件句柄、网络连接句柄数等非常的低；Kafka吞吐量随Topic数增多呈现明显的下降趋势，且资源消耗急剧增大；在SATA盘存储条件下，随着机型的配置提升，inlong吞吐量可以直接压到磁盘瓶颈，而Kafka呈现不稳定状态；在CG1机型SSD盘情况下，Kafka的吞吐量要好于inlong；
-3. 在过滤消费时，inlong可以极大地降低服务端的网络出流量，同时还会因过滤消费消耗的资源少于全量消费，反过来促进inlong吞吐量提升；kafka无服务端过滤，出流量与全量消费一致，流量无明显的节约；
-4. 资源消耗方面各有差异：inlong由于采用顺序写随机读，CPU消耗很大，Kafka采用顺序写块读，CPU消耗很小，但其他资源，如文件句柄、网络连接等消耗非常的大。在实际的SAAS模式下的运营环境里，Kafka会因为zookeeper依赖出现系统瓶颈，会因生产、消费、Broker众多，受限制的地方会更多，比如文件句柄、网络连接数等，资源消耗会更大；
+1. 单Topic单实例配置下，TubeMQ吞吐量要远低于Kafka；单Topic多实例配置下，TubeMQ在4个实例时吞吐量追上Kafka对应5个分区配置，同时TubeMQ的吞吐量随实例数增加而增加，Kafka出现不升反降的情况；TubeMQ可以在系统运行中通过调整各项参数来动态的控制吞吐量的提升；
+2. 多Topic多实例配置下，TubeMQ吞吐量维持在一个非常稳定的范围，且资源消耗，包括文件句柄、网络连接句柄数等非常的低；Kafka吞吐量随Topic数增多呈现明显的下降趋势，且资源消耗急剧增大；在SATA盘存储条件下，随着机型的配置提升，TubeMQ吞吐量可以直接压到磁盘瓶颈，而Kafka呈现不稳定状态；在CG1机型SSD盘情况下，Kafka的吞吐量要好于TubeMQ；
+3. 在过滤消费时，TubeMQ可以极大地降低服务端的网络出流量，同时还会因过滤消费消耗的资源少于全量消费，反过来促进TubeMQ吞吐量提升；kafka无服务端过滤，出流量与全量消费一致，流量无明显的节约；
+4. 资源消耗方面各有差异：TubeMQ由于采用顺序写随机读，CPU消耗很大，Kafka采用顺序写块读，CPU消耗很小，但其他资源，如文件句柄、网络连接等消耗非常的大。在实际的SAAS模式下的运营环境里，Kafka会因为zookeeper依赖出现系统瓶颈，会因生产、消费、Broker众多，受限制的地方会更多，比如文件句柄、网络连接数等，资源消耗会更大；
## 测试环境及配置
###【软件版本及部署环境】
-**角色**|**inlong**|**Kafka**
+**角色**|**TubeMQ**|**Kafka**
:---:|---|---
-**软件版本**|inlong-3.8.0|Kafka\_2.11-0.10.2.0
+**软件版本**|tubemq-3.8.0|Kafka\_2.11-0.10.2.0
**zookeeper部署**|与Broker不在同一台机器上，单机|与Broker配置不在同一台机器，单机
**Broker部署**|单机|单机
**Master部署**|与Broker不在同一台机器上，单机|不涉及
@@ -46,40 +46,40 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
###【Broker系统配置】
-| **配置项** | **inlong Broker** | **Kafka Broker** |
+| **配置项** | **TubeMQ Broker** | **Kafka Broker** |
|:---:|---|---|
| **日志存储** | Raid10处理后的SATA盘或SSD盘 | Raid10处理后的SATA盘或SSD盘 |
-| **启动参数** | BROKER_JVM_ARGS="-Dcom.sun.management.jmxremote -server -Xmx24g -Xmn8g -XX:SurvivorRatio=6 -XX:+UseMembar -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSScavengeBeforeRemark -XX:ParallelCMSThreads=4 -XX:+UseCMSCompactAtFullCollection -verbose:gc -Xloggc:$BASE_DIR/logs/gc.log.`date +%Y-%m-%d-%H-%M-%S` -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+CMSClassUnloadingEnabled -XX:CMSInitiatingOccupancyFraction=75 -XX:CMSFullGCsBeforeCompaction=1 -Dsun.net [...]
-| **配置文件** | 在inlong-3.8.0版本broker.ini配置文件上改动: consumerRegTimeoutMs=35000<br>tcpWriteServiceThread=50<br>tcpReadServiceThread=50<br>primaryPath为SATA盘日志目录|kafka_2.11-0.10.2.0版本server.properties配置文件上改动：<br>log.flush.interval.messages=5000<br>log.flush.interval.ms=10000<br>log.dirs为SATA盘日志目录<br>socket.send.buffer.bytes=1024000<br>socket.receive.buffer.bytes=1024000<br>socket.request.max.bytes=2147483600<br>log.segment.bytes=1073741824<br>num.network.threads=25<br>num.io.threads=48< [...]
+| **启动参数** | BROKER_JVM_ARGS="-Dcom.sun.management.jmxremote -server -Xmx24g -Xmn8g -XX:SurvivorRatio=6 -XX:+UseMembar -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSScavengeBeforeRemark -XX:ParallelCMSThreads=4 -XX:+UseCMSCompactAtFullCollection -verbose:gc -Xloggc:$BASE_DIR/logs/gc.log.`date +%Y-%m-%d-%H-%M-%S` -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+CMSClassUnloadingEnabled -XX:CMSInitiatingOccupancyFraction=75 -XX:CMSFullGCsBeforeCompaction=1 -Dsun.net [...]
+| **配置文件** | 在tubemq-3.8.0版本broker.ini配置文件上改动: consumerRegTimeoutMs=35000<br>tcpWriteServiceThread=50<br>tcpReadServiceThread=50<br>primaryPath为SATA盘日志目录|kafka_2.11-0.10.2.0版本server.properties配置文件上改动：<br>log.flush.interval.messages=5000<br>log.flush.interval.ms=10000<br>log.dirs为SATA盘日志目录<br>socket.send.buffer.bytes=1024000<br>socket.receive.buffer.bytes=1024000<br>socket.request.max.bytes=2147483600<br>log.segment.bytes=1073741824<br>num.network.threads=25<br>num.io.threads=48< [...]
| **其它** | 除测试用例里特别指定，每个topic创建时设置：<br>memCacheMsgSizeInMB=5<br>memCacheFlushIntvl=20000<br>memCacheMsgCntInK=10 <br>unflushThreshold=5000<br>unflushInterval=10000<br>unFlushDataHold=5000 | 客户端代码里设置：<br>生产端：<br>props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");<br>props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");<br>props.put("linger.ms", "200");<br>props.put("block.on.buffer.full", false);<br>props.pu [...]
## 测试场景及结论
-### 场景一：基础场景，单topic情况，一入两出模型，分别使用不同的消费模式、不同大小的消息包，分区逐步做横向扩展，对比inlong和Kafka性能
+### 场景一：基础场景，单topic情况，一入两出模型，分别使用不同的消费模式、不同大小的消息包，分区逐步做横向扩展，对比TubeMQ和Kafka性能
####【结论】
在单topic不同分区的情况下：
-1. inlong吞吐量不随分区变化而变化，同时inlong属于顺序写随机读模式，单实例情况下吞吐量要低于Kafka，CPU要高于Kafka；
+1. TubeMQ吞吐量不随分区变化而变化，同时TubeMQ属于顺序写随机读模式，单实例情况下吞吐量要低于Kafka，CPU要高于Kafka；
2. Kafka随着分区增多吞吐量略有下降，CPU使用率很低；
-3. inlong分区由于是逻辑分区，增加分区不影响吞吐量；Kafka分区为物理文件的增加，但增加分区入出流量反而会下降；
+3. TubeMQ分区由于是逻辑分区，增加分区不影响吞吐量；Kafka分区为物理文件的增加，但增加分区入出流量反而会下降；
####【指标】
-### 场景二：单topic情况，一入两出模型，固定消费包大小，横向扩展实例数，对比inlong和Kafka性能情况
+### 场景二：单topic情况，一入两出模型，固定消费包大小，横向扩展实例数，对比TubeMQ和Kafka性能情况
####【结论】
从场景一和场景二的测试数据结合来看：
-1. inlong随着实例数增多，吞吐量增长，在4个实例的时候吞吐量与Kafka持平，磁盘IO使用率比Kafka低，CPU使用率比Kafka高；
-2. inlong的消费方式影响到系统的吞吐量，内存读取模式（301）性能低于文件读取模式（101），但能降低消息的时延；
+1. TubeMQ随着实例数增多，吞吐量增长，在4个实例的时候吞吐量与Kafka持平，磁盘IO使用率比Kafka低，CPU使用率比Kafka高；
+2. TubeMQ的消费方式影响到系统的吞吐量，内存读取模式（301）性能低于文件读取模式（101），但能降低消息的时延；
3. Kafka随分区实例数增多，没有如期提升系统吞吐量；
-4. inlong按照Kafka等同的增加实例（物理文件）后，吞吐量量随之提升，在4个实例的时候测试效果达到并超过Kafka
- 5个分区的状态；inlong可以根据业务或者系统配置需要，调整数据读取方式，可以动态提升系统的吞吐量；Kafka随着分区增加，入流量有下降；
+4. TubeMQ按照Kafka等同的增加实例（物理文件）后，吞吐量量随之提升，在4个实例的时候测试效果达到并超过Kafka
+ 5个分区的状态；TubeMQ可以根据业务或者系统配置需要，调整数据读取方式，可以动态提升系统的吞吐量；Kafka随着分区增加，入流量有下降；
####【指标】
@@ -89,19 +89,19 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
读取模式通过admin\_upd\_def\_flow\_control\_rule设置qryPriorityId为对应值.
-### 场景三：多topic场景，固定消息包大小、实例及分区数，考察100、200、500、1000个topic场景下inlong和Kafka性能情况
+### 场景三：多topic场景，固定消息包大小、实例及分区数，考察100、200、500、1000个topic场景下TubeMQ和Kafka性能情况
####【结论】
按照多Topic场景下测试：
-1. inlong随着Topic数增加，生产和消费性能维持在一个均线上，没有特别大的流量波动，占用的文件句柄、内存量、网络连接数不多（1k
+1. TubeMQ随着Topic数增加，生产和消费性能维持在一个均线上，没有特别大的流量波动，占用的文件句柄、内存量、网络连接数不多（1k
topic下文件句柄约7500个，网络连接150个），但CPU占用比较大；
-2. inlong通过调整消费方式由内存消费转为文件消费方式后，吞吐量有比较大的增长，CPU占用率有下降，对不同性能要求的业务可以进行区别服务；
+2. TubeMQ通过调整消费方式由内存消费转为文件消费方式后，吞吐量有比较大的增长，CPU占用率有下降，对不同性能要求的业务可以进行区别服务；
3. Kafka随着Topic数的增加，吞吐量有明显的下降，同时Kafka流量波动较为剧烈，长时间运行存消费滞后，以及吞吐量明显下降的趋势，以及内存、文件句柄、网络连接数量非常大(在1K
Topic配置时，网络连接达到了1.2W，文件句柄达到了4.5W)等问题；
-4. 数据对比来看，inlong相比Kafka运行更稳定，吞吐量以稳定形势呈现，长时间跑吞吐量不下降，资源占用少，但CPU的占用需要后续版本解决；
+4. 数据对比来看，TubeMQ相比Kafka运行更稳定，吞吐量以稳定形势呈现，长时间跑吞吐量不下降，资源占用少，但CPU的占用需要后续版本解决；
####【指标】
@@ -112,8 +112,8 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. inlong采用服务端过滤的模式，出流量指标与入流量存在明显差异；
-2. inlong服务端过滤提供了更多的资源给到生产，生产性能比非过滤情况有提升；
+1. TubeMQ采用服务端过滤的模式，出流量指标与入流量存在明显差异；
+2. TubeMQ服务端过滤提供了更多的资源给到生产，生产性能比非过滤情况有提升；
3. Kafka采用客户端过滤模式，入流量没有提升，出流量差不多是入流量的2倍，同时入出流量不稳定；
####【指标】
@@ -121,20 +121,20 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
**注：** 如下场景中，topic为100，包长均为1K，分区数均为10
-### 场景五：inlong、Kafka数据消费时延比对
+### 场景五：TubeMQ、Kafka数据消费时延比对
| 类型 | 时延 | Ping时延 |
|---|---|---|
-| inlong | 90%数据在10ms± | C->B：0.05ms ~ 0.13ms, P->B：2.40ms ~ 2.42ms |
+| TubeMQ | 90%数据在10ms± | C->B：0.05ms ~ 0.13ms, P->B：2.40ms ~ 2.42ms |
| Kafka | 90%集中在250ms± | C->B：0.05ms ~ 0.07ms, P-\>B：2.95ms \~ 2.96ms |
-备注：inlong的消费端存在一个等待队列处理消息追平生产时的数据未找到的情况，缺省有200ms的等待时延。测试该项时，inlong消费端要调整拉取时延（ConsumerConfig.setMsgNotFoundWaitPeriodMs()）为10ms，或者设置频控策略为10ms。
+备注：TubeMQ的消费端存在一个等待队列处理消息追平生产时的数据未找到的情况，缺省有200ms的等待时延。测试该项时，TubeMQ消费端要调整拉取时延（ConsumerConfig.setMsgNotFoundWaitPeriodMs()）为10ms，或者设置频控策略为10ms。
### 场景六：调整Topic配置的内存缓存大小（memCacheMsgSizeInMB）对吞吐量的影响
####【结论】
-1. inlong调整Topic的内存缓存大小能对吞吐量形成正面影响，实际使用时可以根据机器情况合理调整；
+1. TubeMQ调整Topic的内存缓存大小能对吞吐量形成正面影响，实际使用时可以根据机器情况合理调整；
2. 从实际使用情况看，内存大小设置并不是越大越好，需要合理设置该值；
####【指标】
@@ -147,9 +147,9 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. 消费严重滞后情况下，inlong和Kafka都会因磁盘IO飙升使得生产消费受阻；
-2. 在带SSD系统里，inlong可以通过SSD转存储消费来换取部分生产和消费入流量；
-3. 按照版本计划，目前inlong的SSD消费转存储特性不是最终实现，后续版本中将进一步改进，使其达到最合适的运行方式；
+1. 消费严重滞后情况下，TubeMQ和Kafka都会因磁盘IO飙升使得生产消费受阻；
+2. 在带SSD系统里，TubeMQ可以通过SSD转存储消费来换取部分生产和消费入流量；
+3. 按照版本计划，目前TubeMQ的SSD消费转存储特性不是最终实现，后续版本中将进一步改进，使其达到最合适的运行方式；
####【指标】
@@ -160,17 +160,17 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. inlong在BX1机型下较TS60机型有更高的吞吐量，同时因IO util达到瓶颈无法再提升，吞吐量在CG1机型下又较BX1达到更高的指标值；
+1. TubeMQ在BX1机型下较TS60机型有更高的吞吐量，同时因IO util达到瓶颈无法再提升，吞吐量在CG1机型下又较BX1达到更高的指标值；
2. Kafka在BX1机型下系统吞吐量不稳定，且较TS60下测试的要低，在CG1机型下系统吞吐量达到最高，万兆网卡跑满；
-3. 在SATA盘存储条件下，inlong性能指标随着硬件配置的改善有明显的提升；Kafka性能指标随硬件机型的改善存在不升反降的情况;
-4. 在SSD盘存储条件下，Kafka性能指标达到最好，inlong指标不及Kafka；
+3. 在SATA盘存储条件下，TubeMQ性能指标随着硬件配置的改善有明显的提升；Kafka性能指标随硬件机型的改善存在不升反降的情况;
+4. 在SSD盘存储条件下，Kafka性能指标达到最好，TubeMQ指标不及Kafka；
5. CG1机型数据存储盘较小(仅2.2T)，RAID 10配置下90分钟以内磁盘即被写满，无法测试两系统长时间运行情况。
####【指标】
**注1:** 如下场景Topic数均配置500个topic，10个分区，消息包大小为1K字节;
-**注2:** inlong采用的是301内存读取模式消费；
+**注2:** TubeMQ采用的是301内存读取模式消费；
## 附录1 不同机型下资源占用情况图：
diff --git a/docs/zh-cn/architecture.md b/docs/zh-cn/architecture.md
index b852cea..e1febbc 100644
--- a/docs/zh-cn/architecture.md
+++ b/docs/zh-cn/architecture.md
@@ -1,14 +1,14 @@
---
-title: 架构介绍 - Apache inlong
+title: 架构介绍 - Apache TubeMQ
---
-## inlong 架构
-经过多年演变，inlong集群分为如下5个部分：
+## TubeMQ 架构
+经过多年演变，TubeMQ集群分为如下5个部分：
- **Portal**： 负责对外交互和运维操作的Portal部分，包括API和Web两块，API对接集群之外的管理系统，Web是在API基础上对日常运维功能做的页面封装；
-- **Master**： 负责集群控制的Control部分，该部分由1个或多个Master节点组成，Master HA通过Master节点间心跳保活、实时热备切换完成（这是大家使用inlong的Lib时需要填写对应集群所有Master节点地址的原因），主Master负责管理整个集群的状态、资源调度、权限检查、元数据查询等；
+- **Master**： 负责集群控制的Control部分，该部分由1个或多个Master节点组成，Master HA通过Master节点间心跳保活、实时热备切换完成（这是大家使用TubeMQ的Lib时需要填写对应集群所有Master节点地址的原因），主Master负责管理整个集群的状态、资源调度、权限检查、元数据查询等；
- **Broker**： 负责实际数据存储的Store部分，该部分由相互之间独立的Broker节点组成，每个Broker节点对本节点内的Topic集合进行管理，包括Topic的增、删、改、查，Topic内的消息存储、消费、老化、分区扩容、数据消费的offset记录等，集群对外能力，包括Topic数目、吞吐量、容量等，通过水平扩展Broker节点来完成；
@@ -17,15 +17,15 @@ title: 架构介绍 - Apache inlong
- **Zookeeper**： 负责offset存储的zk部分，该部分功能已弱化到仅做offset的持久化存储，考虑到接下来的多节点副本功能该模块暂时保留。- **Zookeeper：** Responsible for the zk part of the offset storage. This part of the function has been weakened to only the persistent storage of the offset. Considering the next multi-node copy function, this module is temporarily reserved;
-## inlong的系统特点
+## TubeMQ的系统特点
- **纯Java实现语言**：
-inlong采用纯Java语言开发，便于开发人员快速熟悉项目及问题处理；
+TubeMQ采用纯Java语言开发，便于开发人员快速熟悉项目及问题处理；
- **引入协调节点**：
-inlong系统采用自管理的元数据仲裁机制方式进行，Master节点通过采用内嵌数据库BDB完成集群内元数据的存储、更新以及HA热切功能，负责inlong集群的运行管控和配置管理操作，对外提供接口等；通过Master节点，inlong集群里的Broker配置设置、变更及查询实现了完整的自动化闭环管理，减轻了系统维护的复杂度；
+TubeMQ系统采用自管理的元数据仲裁机制方式进行，Master节点通过采用内嵌数据库BDB完成集群内元数据的存储、更新以及HA热切功能，负责TubeMQ集群的运行管控和配置管理操作，对外提供接口等；通过Master节点，TubeMQ集群里的Broker配置设置、变更及查询实现了完整的自动化闭环管理，减轻了系统维护的复杂度；
- **服务器侧消费负载均衡**：
-inlong采用的是服务侧负载均衡的方案，而不是客户端侧操作，提升系统的管控能力同时简化客户端实现，更便于均衡算法升级；
+TubeMQ采用的是服务侧负载均衡的方案，而不是客户端侧操作，提升系统的管控能力同时简化客户端实现，更便于均衡算法升级；
- **系统行级锁操作**：
对于Broker消息读写中存在中间状态的并发操作采用行级锁，避免重复问题；
@@ -34,7 +34,7 @@ inlong采用的是服务侧负载均衡的方案，而不是客户端侧操作
Offset由各个Broker独自管理，ZK只作数据持久化存储用（最初考虑完全去掉ZK依赖，考虑到后续的功能扩展就暂时保留）；
- **消息读取机制的改进**：
-inlong采用消息随机读取模式,同时为了降低消息时延又增加了内存缓存读写,使其满足业务快速生产消费的需求（后面章节详细介绍）；
+TubeMQ采用消息随机读取模式,同时为了降低消息时延又增加了内存缓存读写,使其满足业务快速生产消费的需求（后面章节详细介绍）；
- **消费者行为管控**：
支持通过策略实时动态地控制系统接入的消费者行为，包括系统负载高时对特定业务的限流、暂停消费，动态调整数据拉取的频率等；
@@ -43,20 +43,20 @@ inlong采用消息随机读取模式,同时为了降低消息时延又增加了
针对系统运维、业务特点、机器负载状态的不同需求，系统支持运维通过策略来动态控制不同消费者的消费行为，比如是否有权限消费、消费时延分级保证、消费限流控制，以及数据拉取频率控制等；
- **系统安全管控**：
-根据业务不同的数据服务需要，以及系统运维安全的考虑，inlong系统增加了TLS传输层加密管道，生产和消费服务的认证、授权，以及针对分布式访问控制的访问令牌管理，满足业务和系统运维在系统安全方面的需求；
+根据业务不同的数据服务需要，以及系统运维安全的考虑，TubeMQ系统增加了TLS传输层加密管道，生产和消费服务的认证、授权，以及针对分布式访问控制的访问令牌管理，满足业务和系统运维在系统安全方面的需求；
- **资源利用率提升改进**：
-inlong采用连接复用模式，减少连接资源消耗；通过逻辑分区构造，减少系统对文件句柄数的占用，通过服务器端过滤模式，减少网络带宽资源使用率；通过剥离对Zookeeper的使用，减少Zookeeper的强依赖及瓶颈限制；
+TubeMQ采用连接复用模式，减少连接资源消耗；通过逻辑分区构造，减少系统对文件句柄数的占用，通过服务器端过滤模式，减少网络带宽资源使用率；通过剥离对Zookeeper的使用，减少Zookeeper的强依赖及瓶颈限制；
- **客户端改进**：
基于业务使用上的便利性以，我们简化了客户端逻辑，使其做到最小的功能集合，我们采用基于响应消息的接收质量统计算法来自动剔出坏的Broker节点，基于首次使用时作连接尝试来避免大数据量发送时发送受阻（具体内容见后面章节介绍）。
## Broker文件存储方案改进
-以磁盘为数据持久化媒介的系统都面临各种因磁盘问题导致的系统性能问题，inlong系统也不例外，性能提升很大程度上是在解决消息数据如何读写及存储的问题，在这个方面inlong进行了比较多的改进：
+以磁盘为数据持久化媒介的系统都面临各种因磁盘问题导致的系统性能问题，TubeMQ系统也不例外，性能提升很大程度上是在解决消息数据如何读写及存储的问题，在这个方面TubeMQ进行了比较多的改进：
### 文件结构组织形式调整
- inlong的磁盘存储方案类似Kafka，但又不尽相同，如下图示，存储实例由一个索引文件和一个数据文件组成，每个Topic可以分配1个或者多个存储实例，每个Topic单独维护管理存储实例的相关机制，包括老化周期，partition个数，是否可读可写等。
+ TubeMQ的磁盘存储方案类似Kafka，但又不尽相同，如下图示，存储实例由一个索引文件和一个数据文件组成，每个Topic可以分配1个或者多个存储实例，每个Topic单独维护管理存储实例的相关机制，包括老化周期，partition个数，是否可读可写等。
### 内存块缓存
@@ -64,19 +64,19 @@ inlong采用连接复用模式，减少连接资源消耗；通过逻辑分区
-## inlong客户端的演进： ##
-业务与inlong接触得最多的是消费侧，怎样更适应业务特点、更方便业务使用我们在这块做了比较多的改进：
+## TubeMQ客户端的演进： ##
+业务与TubeMQ接触得最多的是消费侧，怎样更适应业务特点、更方便业务使用我们在这块做了比较多的改进：
- **数据拉取模式支持Push、Pull：**
- - **Push客户端：** inlong最初消费端版本只提供Push模式的消费，这种模式能比较快速地消费数据，减轻服务端压力，但同时也带来一个问题，业务使用的时候因为无法控制拉取频率，从而容易形成数据积压数据处理不过来；
+ - **Push客户端：** TubeMQ最初消费端版本只提供Push模式的消费，这种模式能比较快速地消费数据，减轻服务端压力，但同时也带来一个问题，业务使用的时候因为无法控制拉取频率，从而容易形成数据积压数据处理不过来；
- **带消费中止/继续的Push客户端：** 在收到业务反馈能否控制Push拉取动作的需求后，我们增加了resumeConsume()/pauseConsume()函数对，让业务可以模拟水位线控制机制，状态比较繁忙时调用pauseConsume()函数来中止Lib后台的数据拉取，在状态恢复后，再调用resumeConsume()通知Lib后台继续拉取数据；
- **Pull客户端：** 我们后来版本里增加了Pull客户端，该客户端有别于Push客户端，是由业务而非Lib主动的拉取消息并对数据处理的结果进行成功与否的确认，将数据处理的主动权留给业务。这样处理后，虽然服务端压力有所提升，但业务消费时积压情况可大大缓解。
-- **数据消费行为支持顺序和过滤消费：** 在inlong设计初我们考虑是不同业务使用不同的Topic，实际运营中我们发现不少业务实际上是通过代理模式上报的数据，数据通过Topic下的文件ID或者表ID属性来区分，业务为了消费自己的一份数据是需要全量消费该Topic下的所有数据。我们通过tid字段支持指定属性的过滤消费模式，将数据过滤放到服务端来做，减少出流量以及客户端的数据处理压力。
+- **数据消费行为支持顺序和过滤消费：** 在TubeMQ设计初我们考虑是不同业务使用不同的Topic，实际运营中我们发现不少业务实际上是通过代理模式上报的数据，数据通过Topic下的文件ID或者表ID属性来区分，业务为了消费自己的一份数据是需要全量消费该Topic下的所有数据。我们通过tid字段支持指定属性的过滤消费模式，将数据过滤放到服务端来做，减少出流量以及客户端的数据处理压力。
-- **支持业务exactly-once消费：** 为了解决业务处理数据时需要精确回档的需求，在客户端版本里提供了通过客户端重置精确offset功能，业务重启系统时，只需通过客户端提供待回拨时间点的消费上下文，inlong即可按照指定的精确位置接续消费。该特性目前已在Flink这类实时计算框架使用，依托Flink基于checkpoint机制进行exactly-once数据处理。
+- **支持业务exactly-once消费：** 为了解决业务处理数据时需要精确回档的需求，在客户端版本里提供了通过客户端重置精确offset功能，业务重启系统时，只需通过客户端提供待回拨时间点的消费上下文，TubeMQ即可按照指定的精确位置接续消费。该特性目前已在Flink这类实时计算框架使用，依托Flink基于checkpoint机制进行exactly-once数据处理。
---
diff --git a/docs/zh-cn/client_rpc.md b/docs/zh-cn/client_rpc.md
index 0a93f3c..6faeba6 100644
--- a/docs/zh-cn/client_rpc.md
+++ b/docs/zh-cn/client_rpc.md
@@ -1,17 +1,17 @@
---
-title: 客户端RPC - Apache inlong
+title: 客户端RPC - Apache TubeMQ
---
-# Apache inlong RPC定义：
+# Apache TubeMQ RPC定义：
## 总体介绍：
-这部分介绍内容在/org/apache/inlong/corerpc模块下可以找到对应实现，Apache inlong 各个节点间（Client、Master、Broker）通过TCP协议长连接交互，其消息采用的是 【二进制 + Protobuf编码】组合方式进行定义，如下图示：
+这部分介绍内容在/org/apache/tubemq/corerpc模块下可以找到对应实现，Apache TubeMQ 各个节点间（Client、Master、Broker）通过TCP协议长连接交互，其消息采用的是 【二进制 + Protobuf编码】组合方式进行定义，如下图示：
在TCP里我们看到的都是二进制流，我们定义了4字节的msgToken消息头字段RPC\_PROTOCOL\_BEGIN\_TOKEN，用来区分每一条消息以及识别对端的合法性，客户端收到的消息不是以该字段开始的响应消息时，说明连接方非本系统支持的协议，或者返回数据出现了异常，这个时候需要关闭该连接，提示错误退出或者重连；紧接着的是4字节的消息序列号serialNo，该字段由请求方生成通过请求消息携带给服务端，服务器端完成该请求消息服务后通过请求消息的对应响应消息原样返回，主要用于客户端关联请求响应的上下文；4字节的listSize字段表示接下来按照PB编码的数据块个数，即后面跟随的[\<len\>\<data\>]内容的块数，目前协议定义下该字段不为0；[\<len\>\<data\>]是2个字段组合，即数据块长度，数据，主要是表示这个数据块长度及具体的数据。
-为什么会以listSize [\<len\>\<data\>]形式定义pb数据内容？因为在inlong的这个实现中，序列化后的PB数据是通过ByteBuffer对象保存的，Java里ByteBuffer存在一个最大块长8196，超过单个块长度的PB消息内容就需要用多个ByteBuffer保存，序列化到TCP消息时候，这块没有统计总长，直接按照PB序列化的ByteBuffer列表写入到了消息中。 **在多语言实现时候，这块需要特别注意：** 需要将PB数据内容序列化成块数组（pb编解码里有对应支持）。
+为什么会以listSize [\<len\>\<data\>]形式定义pb数据内容？因为在TubeMQ的这个实现中，序列化后的PB数据是通过ByteBuffer对象保存的，Java里ByteBuffer存在一个最大块长8196，超过单个块长度的PB消息内容就需要用多个ByteBuffer保存，序列化到TCP消息时候，这块没有统计总长，直接按照PB序列化的ByteBuffer列表写入到了消息中。 **在多语言实现时候，这块需要特别注意：** 需要将PB数据内容序列化成块数组（pb编解码里有对应支持）。
## PB格式编码：
@@ -22,7 +22,7 @@ PB格式编码分为RPC框架定义，到Master的消息编码和到Broker的消
RPC.proto定义了6个结构，分为2大类：请求消息与响应消息，响应消息里又分为正常的响应返回以及抛异常情况下的响应返回：
-请求消息编码及响应消息解码可以参考NettyClient.java类实现，这个部分的定义存在一些改进空间，具体见【[inlong-109](https://issues.apache.org/jira/browse/inlong-109)】，但由于兼容性考虑，会逐步的替换，我们按照当前proto版本实现至少在1.0.0版本前交互不是问题，但1.0.0时会考虑用新协议，协议实现模块需要各个SDK预留出改进空间。以请求消息填写为例，RpcConnHeader等相关结构如下：
+请求消息编码及响应消息解码可以参考NettyClient.java类实现，这个部分的定义存在一些改进空间，具体见【[TUBEMQ-109](https://issues.apache.org/jira/browse/TUBEMQ-109)】，但由于兼容性考虑，会逐步的替换，我们按照当前proto版本实现至少在1.0.0版本前交互不是问题，但1.0.0时会考虑用新协议，协议实现模块需要各个SDK预留出改进空间。以请求消息填写为例，RpcConnHeader等相关结构如下：
其中flag标记的是否请求消息，后面3个标记的是消息跟踪的相关内容，目前没有使用；相关的服务类型，协议版本，服务类型等是固定的映射关系，比较关键的一个参数RequestBody.timeout是一个请求被服务器收到到实际处理时的最大允许等待时间长，超过就丢弃，目前缺省为10秒，请求填写具体见如下部分：
@@ -52,7 +52,7 @@ Producer在系统中一共4对指令，到master是要做注册，心跳，退
Consumer一共7对指令，到master是要做注册，心跳，退出操作；到broker包括注册，注销，心跳，拉取消息，确认消息4对，其中到Broker的注册注销是同一个命令，用了不同的状态码表示：
-从上图我们可以看到，Consumer首先要注册到Master，但注册到Master时并没有立即获取到元数据信息，原因是inlong是采用的是服务器端负载均衡模式，客户端需要等待服务器派发消费分区信息；Consumer到Broker需要进行注册注销操作，原因在于消费时候分区是独占消费，即同一时刻同一分区者只能被同组的一个消费者进行消费，为了解决这个问题，需要客户端进行注册，获得分区的消费权限；消息拉取与消费确认需要成对出现，虽然协议支持多次拉取然后最后一次确认处理，但从客户端可能超时丢失分区的消费权限，从而导致数据回滚重复消费触发，数据积攒的越多重复消费的量就越多，所以按照1：1的提交比较合适。
+从上图我们可以看到，Consumer首先要注册到Master，但注册到Master时并没有立即获取到元数据信息，原因是TubeMQ是采用的是服务器端负载均衡模式，客户端需要等待服务器派发消费分区信息；Consumer到Broker需要进行注册注销操作，原因在于消费时候分区是独占消费，即同一时刻同一分区者只能被同组的一个消费者进行消费，为了解决这个问题，需要客户端进行注册，获得分区的消费权限；消息拉取与消费确认需要成对出现，虽然协议支持多次拉取然后最后一次确认处理，但从客户端可能超时丢失分区的消费权限，从而导致数据回滚重复消费触发，数据积攒的越多重复消费的量就越多，所以按照1：1的提交比较合适。
## 客户端功能集合：
@@ -163,7 +163,7 @@ Java的SDK版本里ClientId = 节点IP地址（IPV4） + "-" + 进程I
**分区负载均衡过程**:
----------
-Apache inlong目前采用的是服务器端负载均衡模式，均衡过程由服务器管理维护；后续版本会增加客户端负载均衡模式，形成2种模式共存的情况，由业务根据需要选择不同的均衡方式。
+Apache TubeMQ目前采用的是服务器端负载均衡模式，均衡过程由服务器管理维护；后续版本会增加客户端负载均衡模式，形成2种模式共存的情况，由业务根据需要选择不同的均衡方式。
**服务器端负载均衡过程如下**：
diff --git a/docs/zh-cn/clients_java.md b/docs/zh-cn/clients_java.md
index 5ead7ee..08cea7b 100644
--- a/docs/zh-cn/clients_java.md
+++ b/docs/zh-cn/clients_java.md
@@ -1,8 +1,8 @@
---
-title: JAVA SDK API介绍 - Apache inlong
+title: JAVA SDK API介绍 - Apache TubeMQ
---
-## **inlong Lib** **接口使用**
+## **TubeMQ Lib** **接口使用**
------
@@ -12,19 +12,19 @@ title: JAVA SDK API介绍 - Apache inlong
#### **a) MessageSessionFactory（消息会话工厂）：**
-inlong 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
+TubeMQ 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
#### **b) MasterInfo:**
-inlong的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于inlong Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于inlong的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
+TubeMQ的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于TubeMQ Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于TubeMQ的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
#### **c) TubeClientConfig：**
-MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与inlong-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前inlong的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
+MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与TubeMQ-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前TubeMQ的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
@@ -36,7 +36,7 @@ ConsumerConfig类是TubeClientConfig类的子类，它是在TubeClientConfig类
#### **e) Message：**
-Message类是inlong里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与inlong系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增inlong系统填写的内容，并在后续的版本中，新增的inlong系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做inlong进行数据收发统计时消息时间统计维度用。
+Message类是TubeMQ里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与TubeMQ系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增TubeMQ系统填写的内容，并在后续的版本中，新增的TubeMQ系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做TubeMQ进行数据收发统计时消息时间统计维度用。
@@ -48,7 +48,7 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **g) MessageConsumer：**
-该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上inlong是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
+该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上TubeMQ是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
- a. CompleteSubscribe接口，带参数的接口支持客户端对指定的分区进行指定offset消费，不带参数的接口则按照ConsumerConfig.setConsumeModel(int consumeModel)接口进行对应的消费模式设置来消费数据;
@@ -64,13 +64,13 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **a) 环境准备：**
-inlong开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的inlong集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
+TubeMQ开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的TubeMQ集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
#### **b) 创建Consumer：**
-见包org.apache.inlong.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
+见包org.apache.tubemq.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
- ###### **i.初始化MessageConsumerExample类：**
@@ -172,7 +172,7 @@ public class DefaultMessageListener implements MessageV2Listener {
#### **c) 创建Producer：**
-现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用inlong进行使用的场景，这里提供对应的使用demo，见包org.apache.inlong.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的inlong集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
+现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用TubeMQ进行使用的场景，这里提供对应的使用demo，见包org.apache.tubemq.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的TubeMQ集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
- **i. 初始化MessageProducerExample类：**
@@ -218,7 +218,7 @@ public void publishTopics(List<String> topicList) throws TubeClientException {
- **iii. 进行数据生产：**
-如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《inlong错误信息介绍.xlsx》：
+如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《TubeMQ错误信息介绍.xlsx》：
```java
public void sendMessageAsync(int id, long currtime,
@@ -248,7 +248,7 @@ public void sendMessageAsync(int id, long currtime,
- **iv. Producer不同类MAMessageProducerExample关注点：**
-该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（inlong通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
+该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（TubeMQ通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
diff --git a/docs/zh-cn/configure_introduction.md b/docs/zh-cn/configure_introduction.md
index 2bf8451..42f0472 100644
--- a/docs/zh-cn/configure_introduction.md
+++ b/docs/zh-cn/configure_introduction.md
@@ -1,12 +1,12 @@
---
-title: 配置参数介绍 - Apache inlong
+title: 配置参数介绍 - Apache TubeMQ
---
-# inlong服务端配置文件说明：
+# TubeMQ服务端配置文件说明：
-inlong服务端包括Master和Broker共2个模块，Master又包含供外部页面访问的Web前端模块（该部分存放在resources中），考虑到实际部署时2个模块常常部署在同1台机器中，inlong将2个模块3个部分的内容打包在一起交付给运维使用；客户端则不包含服务端部分的lib包单独交付给业务使用。
+TubeMQ服务端包括Master和Broker共2个模块，Master又包含供外部页面访问的Web前端模块（该部分存放在resources中），考虑到实际部署时2个模块常常部署在同1台机器中，TubeMQ将2个模块3个部分的内容打包在一起交付给运维使用；客户端则不包含服务端部分的lib包单独交付给业务使用。
-Master与Broker采用ini配置文件格式，相关配置文件分别放置在inlong-server-3.8.0/conf/目录的master.ini和broker.ini文件中：
+Master与Broker采用ini配置文件格式，相关配置文件分别放置在tubemq-server-3.8.0/conf/目录的master.ini和broker.ini文件中：
@@ -48,12 +48,12 @@ Master除了后端系统配置文件外，还在resources里存放了Web前端
| startConsumeAuthenticate | 否 | boolean | 是否启用消费端用户认证，缺省为false |
| startConsumeAuthorize | 否 | boolean | 是否启用消费端消费授权认证，缺省为false |
| maxGroupBrokerConsumeRate | 否 | int | 集群Broker数与消费组里成员数的最大比值，可选项，缺省为50，50台Broker集群里允许1个消费组最少启动1个客户端消费 |
-| metaDataPath | 否 | String | Metadata存储路径，可以是绝对路径、或者相对inlong安装目录（"$BASE_DIR"）的相对路径。缺省为"var/meta_data" |
+| metaDataPath | 否 | String | Metadata存储路径，可以是绝对路径、或者相对TubeMQ安装目录（"$BASE_DIR"）的相对路径。缺省为"var/meta_data" |
|
|
-| [zookeeper] | Master对应的inlong集群存储Offset的ZooKeeper集群相关信息，必填单元，值固定为"[zookeeper]" |
+| [zookeeper] | Master对应的TubeMQ集群存储Offset的ZooKeeper集群相关信息，必填单元，值固定为"[zookeeper]" |
| [zookeeper] | zkServerAddr | 否 | String | zk服务器地址，可选配置，缺省为"localhost:2181" |
-| zkNodeRoot | 否 | String | zk上的节点根目录路径，可选配置，缺省为"/inlong" |
+| zkNodeRoot | 否 | String | zk上的节点根目录路径，可选配置，缺省为"/tubemq" |
| zkSessionTimeoutMs | 否 | long | zk心跳超时，单位毫秒，默认30秒 |
| zkConnectionTimeoutMs | 否 | long | zk连接超时时间，单位毫秒，默认30秒 |
| zkSyncTimeMs | 否 | long | zk数据同步时间，单位毫秒，默认5秒 |
@@ -61,7 +61,7 @@ Master除了后端系统配置文件外，还在resources里存放了Web前端
|
|
| [replication] | 集群数据复制的相关配置，用于实现元数据多节点热备，必填单元，值固定为"[replication]" |
-| [replication] | repGroupName | 否 | String | 集群名，所属主备Master节点值必须相同，可选字段，缺省为"inlongMasterGroup" |
+| [replication] | repGroupName | 否 | String | 集群名，所属主备Master节点值必须相同，可选字段，缺省为"tubemqMasterGroup" |
| repNodeName | 是 | String | 所属Master在集群中的节点名，该值各个节点必须不重复，必填字段 |
| repNodePort | 否 | int | 节点复制通讯端口，可选字段，缺省为9001 |
| repHelperHost | 否 | String | 集群启动时的主节点，可选字段，缺省为"127.0.0.1:9001" |
@@ -130,7 +130,7 @@ Master除了后端系统配置文件外，还在resources里存放了Web前端
|
| [zookeeper] | Broker对应的Tube MQ集群存储Offset的ZooKeeper集群相关信息，必填单元，值固定为"[zookeeper]" |
| [zookeeper] | zkServerAddr | 否 | String | zk服务器地址，可选配置，缺省为"localhost:2181" |
-| zkNodeRoot | 否 | String | zk上的节点根目录路径，可选配置，缺省为"/inlong" |
+| zkNodeRoot | 否 | String | zk上的节点根目录路径，可选配置，缺省为"/tubemq" |
| zkSessionTimeoutMs | 否 | long | zk心跳超时，单位毫秒，默认30秒 |
| zkConnectionTimeoutMs | 否 | long | zk连接超时时间，单位毫秒，默认30秒 |
| zkSyncTimeMs | 否 | long | zk数据同步时间，单位毫秒，默认5秒 |
diff --git a/docs/zh-cn/console_introduction.md b/docs/zh-cn/console_introduction.md
index 798e671..69591f2 100644
--- a/docs/zh-cn/console_introduction.md
+++ b/docs/zh-cn/console_introduction.md
@@ -1,23 +1,23 @@
---
-title: 管控台操作指引 - Apache inlong
+title: 管控台操作指引 - Apache TubeMQ
---
-# inlong管控台操作指引
+# TubeMQ管控台操作指引
## 管控台关系
- inlong管控台是管理inlong集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与inlong系统相关的运营数据及操作。需要说明的是，当前提供的inlong前台所提供的功能没有涵盖inlong所提供的功能范围，大家可以参照《inlong HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。inlong管控台的访问地址为http://portal:webport/config/topic_list.htm：
+ TubeMQ管控台是管理TubeMQ集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与TubeMQ系统相关的运营数据及操作。需要说明的是，当前提供的TubeMQ前台所提供的功能没有涵盖TubeMQ所提供的功能范围，大家可以参照《TubeMQ HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。TubeMQ管控台的访问地址为http://portal:webport/config/topic_list.htm：
其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。
-## inlong管控台各版面介绍
+## TubeMQ管控台各版面介绍
管控台一共3项内容：分发查询，配置管理，集群管理；配置管理又分为Broker列表，Topic列表2个部分，我们先介绍简单的分发查询和集群管理，然后再介绍复杂的配置管理。
### 分发查询
- 点分发查询，我们会看到如下的列表信息，这是当前inlong集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
+ 点分发查询，我们会看到如下的列表信息，这是当前TubeMQ集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
点击记录，可以看到选中的消费组里的消费者成员，及对应消费的Broker及Partition分区信息，如下图示：
@@ -36,22 +36,22 @@ title: 管控台操作指引 - Apache inlong
从页面信息我们也可以看到，除了Broker的记录信息外，还有Broker在该集群里的管理信息，包括是否已上线，是否处于命令处理中，是否可读，是否可写，配置是否做了更改，是否已加载变更的配置信息。
- 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《inlong HTTP访问接口定义.xls》
+ 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《TubeMQ HTTP访问接口定义.xls》
- 所有inlong管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
+ 所有TubeMQ管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
-## inlong管控台上涉及的操作及注意事项
+## TubeMQ管控台上涉及的操作及注意事项
- 如上所说，inlong管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类inlong集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
+ 如上所说，TubeMQ管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类TubeMQ集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
- 1． **inlong集群做扩缩容增、减Broker节点时，要先在inlong管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
+ 1． **TubeMQ集群做扩缩容增、减Broker节点时，要先在TubeMQ管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
- inlong集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。inlong管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
+ TubeMQ集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。TubeMQ管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
2． **Topic元数据信息需要通过套件的业务使用界面进行新增和删除操作：**
- 如下图，业务发现自己消费的Topic在inlong管控台上没有，则需要在inlong的管控台上直接操作：
+ 如下图，业务发现自己消费的Topic在TubeMQ管控台上没有，则需要在TubeMQ的管控台上直接操作：
我们通过如上图中的Topic列表项完成Topic的新增，会弹出如下框，
diff --git a/docs/zh-cn/consumer_example.md b/docs/zh-cn/consumer_example.md
index 82dfef7..9811b77 100644
--- a/docs/zh-cn/consumer_example.md
+++ b/docs/zh-cn/consumer_example.md
@@ -1,9 +1,9 @@
---
-title: 消费者示例 - Apache inlong
+title: 消费者示例 - Apache TubeMQ
---
## Consumer 示例
- inlong 提供了两种方式来消费消息： PullConsumer and PushConsumer。
+ TubeMQ 提供了两种方式来消费消息： PullConsumer and PushConsumer。
### PullConsumer
diff --git a/docs/zh-cn/contact.md b/docs/zh-cn/contact.md
index 610025e..16235a8 100644
--- a/docs/zh-cn/contact.md
+++ b/docs/zh-cn/contact.md
@@ -1,5 +1,5 @@
---
-title: 联系我们 - Apache inlong
+title: 联系我们 - Apache TubeMQ
---
联系我们
@@ -9,10 +9,10 @@ title: 联系我们 - Apache inlong
| Name | Scope | | | |
|:------------------------------------------------------------------------------|:--------------------------------|:----------------------------------------------------------------|:--------------------------------------------------------------------|:-----------------------------------------------------------------------------|
- | [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
+ | [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@tubemq.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@tubemq.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/tubemq-dev/) |
-- 项目主页: https://inlong.apache.org
-- 需求与问题: https://issues.apache.org/jira/browse/inlong
+- 项目主页: https://tubemq.apache.org
+- 需求与问题: https://issues.apache.org/jira/browse/TubeMQ
diff --git a/docs/zh-cn/deployment.md b/docs/zh-cn/deployment.md
index 16e45c4..0f4a0fb 100644
--- a/docs/zh-cn/deployment.md
+++ b/docs/zh-cn/deployment.md
@@ -1,8 +1,8 @@
---
-title: 部署指引 - Apache inlong
+title: 部署指引 - Apache TubeMQ
---
-# inlong编译、部署及简单使用：
+# TubeMQ编译、部署及简单使用：
## 工程编译打包：
@@ -12,7 +12,7 @@ title: 部署指引 - Apache inlong
mvn clean package -Dmaven.test.skip
```
-例如将inlong源码包放在E盘根目录，按照如下方式执行上述命令，当各个子目录都编译成功时工程编译完成：
+例如将TubeMQ源码包放在E盘根目录，按照如下方式执行上述命令，当各个子目录都编译成功时工程编译完成：
@@ -20,11 +20,11 @@ mvn clean package -Dmaven.test.skip
**部署服务端：**
-如上例子，进入E:\GIT\inlong\inlong-server\target目录，服务侧的相关内容如下，其中inlong-server-3.8.0-bin.tar.gz为完整的服务端安装包，里面包括执行脚本，配置文件，依赖包，以及前端的源码；inlong-server-3.8.0.jar为服务端处理逻辑包，包含于完整工程安装包的lib里，单独提出是考虑到日常变更升级时改动点多在服务器处理逻辑上，升级的时候只需要单独替换该jar包即可：
+如上例子，进入E:\GIT\TubeMQ\tubemq-server\target目录，服务侧的相关内容如下，其中tubemq-server-3.8.0-bin.tar.gz为完整的服务端安装包，里面包括执行脚本，配置文件，依赖包，以及前端的源码；tubemq-server-3.8.0.jar为服务端处理逻辑包，包含于完整工程安装包的lib里，单独提出是考虑到日常变更升级时改动点多在服务器处理逻辑上，升级的时候只需要单独替换该jar包即可：
-这里我们是全新安装，将上述完整的工程安装包部署到待安装机器上，我们这里是放置在/data/inlong目录下：
+这里我们是全新安装，将上述完整的工程安装包部署到待安装机器上，我们这里是放置在/data/tubemq目录下：
@@ -37,7 +37,7 @@ mvn clean package -Dmaven.test.skip
| --- | --- | --- | --- | --- | --- |
| 10.224.148.145 | **Master** | 8099 | 8199 | 8080 | 元数据存储在`/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | 消息储存在`/stage/msgdata` |
-| | ZK | 2181 | | | Offset储存在根目录`/inlong` |
+| | ZK | 2181 | | | Offset储存在根目录`/tubemq` |
| 100.115.158.208 | **Master** | 8099 | 8199 | 8080 | 元数据存储在 `/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | 消息储存在`/stage/msgdata` |
| 10.224.155.80 | Producer ||||
@@ -62,7 +62,7 @@ mvn clean package -Dmaven.test.skip
**启动Master**：
-完成如上配置设置后，首先进入主备Master所在的inlong环境的bin目录，进行服务启动操作：
+完成如上配置设置后，首先进入主备Master所在的TubeMQ环境的bin目录，进行服务启动操作：
@@ -76,7 +76,7 @@ mvn clean package -Dmaven.test.skip
**启动Broker**：
-启动Broker和启动master有些差别：Master负责管理整个inlong集群，包括Broker节点运行管理以及节点上部署的Topic配置管理，还有生产和消费管理等，因此，实体的Broker启动前，首先要在Master上配置Broker元数据，增加Broker相关的管理信息，如下图示：
+启动Broker和启动master有些差别：Master负责管理整个TubeMQ集群，包括Broker节点运行管理以及节点上部署的Topic配置管理，还有生产和消费管理等，因此，实体的Broker启动前，首先要在Master上配置Broker元数据，增加Broker相关的管理信息，如下图示：
@@ -116,7 +116,7 @@ Master上所有的变更操作在点击确认的时候，都会弹出如上输
配置Topic和配置Broker信息类似，都需要先在Master上新增元数据信息，然后才能开始使用，要不生产和消费时候会报topic不存在错误，如我们用安装包里的example对不存在的Topic名test进行生产：
```
-/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
Demo实例会报如下错误信息：
@@ -142,16 +142,16 @@ Demo实例会报如下错误信息：
**数据生产和消费**：
-在安装包里，我们打包了example的测试Demo，业务也可以直接使用inlong-client-3.8.0.jar封装自己的生产和消费逻辑，总的形式是类似，我们先执行生产者的Demo，我们可以看到Broker上已开始有数据接收：
+在安装包里，我们打包了example的测试Demo，业务也可以直接使用tubemq-client-3.8.0.jar封装自己的生产和消费逻辑，总的形式是类似，我们先执行生产者的Demo，我们可以看到Broker上已开始有数据接收：
```
- /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+ /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
我们再执行消费Demo，我们也可以看到消费也正常：
```
- /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
+ /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
```
@@ -161,4 +161,4 @@ Demo实例会报如下错误信息：
-在这里，已经完成了inlong的编译，部署，系统配置，启动，生产和消费。如果需要了解更深入的内容，就需要查看《inlong HTTP API》里的相关内容，进行相应的配置设置。
\ No newline at end of file
+在这里，已经完成了TubeMQ的编译，部署，系统配置，启动，生产和消费。如果需要了解更深入的内容，就需要查看《TubeMQ HTTP API》里的相关内容，进行相应的配置设置。
\ No newline at end of file
diff --git a/docs/zh-cn/development/how-to-become-a-committer.md b/docs/zh-cn/development/how-to-become-a-committer.md
index 720d80c..704b031 100644
--- a/docs/zh-cn/development/how-to-become-a-committer.md
+++ b/docs/zh-cn/development/how-to-become-a-committer.md
@@ -1,19 +1,19 @@
---
-title: 如何成为Committer - Apache inlong
+title: 如何成为Committer - Apache TubeMQ
---
-# 如何成为inlong Committer 和 PPMC
+# 如何成为TubeMQ Committer 和 PPMC
-> Apache inlong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
-Apache inlong Committer拥有inlong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache inlong Committer。
+> Apache TubeMQ是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
+Apache TubeMQ Committer拥有TubeMQ代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache TubeMQ Committer。
-任何人只要对inlong项目做了贡献，那你就是官方承认的inlong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
+任何人只要对TubeMQ项目做了贡献，那你就是官方承认的TubeMQ项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，
或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。
潜在贡献清单（无特定顺序）：
- 提交自己发现的Bug、特性、改进到issue
-- 更新官方文档使项目的文档是最近的、撰写inlong的最佳实践、特性剖析的各种对用户有用的文档
+- 更新官方文档使项目的文档是最近的、撰写TubeMQ的最佳实践、特性剖析的各种对用户有用的文档
- 执行测试并报告测试结果，性能测试与其他MQ的性能对比测试等
- 发布版本时，积极参与投票
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
@@ -21,15 +21,15 @@ Apache inlong Committer拥有inlong代码库的写权限，可以合并PR，任
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
-- 发表关于inlong的演讲和博客，并将这些添加到inlong的官方网站
-- 有利于inlong社区发展的任何贡献
+- 发表关于TubeMQ的演讲和博客，并将这些添加到TubeMQ的官方网站
+- 有利于TubeMQ社区发展的任何贡献
- ......
更多可以参考：[ASF官方文档](https://community.apache.org/contributors/)
并不是每个人都能完成这个清单上的所有（甚至任何）项目。如果你想用其他方式来做贡献，那就去做吧（并把它们添加到列表中）。
-愉快的举止和乐于奉献的精神是您对inlong项目产生积极影响所需要的全部。
-邀请您成为Committer是您与社区长期稳定互动的结果，是inlong社区对您的信任和认可。
+愉快的举止和乐于奉献的精神是您对TubeMQ项目产生积极影响所需要的全部。
+邀请您成为Committer是您与社区长期稳定互动的结果，是TubeMQ社区对您的信任和认可。
Committer有义务审查(Review)和合并(merge)其他人提交的PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
-当你足够活跃且对社区的贡献比较大后，就可以晋升为inlong项目的PPMC成员。
+当你足够活跃且对社区的贡献比较大后，就可以晋升为TubeMQ项目的PPMC成员。
diff --git a/docs/zh-cn/development/how-to-commit.md b/docs/zh-cn/development/how-to-commit.md
index 1877460..25368cc 100644
--- a/docs/zh-cn/development/how-to-commit.md
+++ b/docs/zh-cn/development/how-to-commit.md
@@ -1,17 +1,17 @@
---
-title: 如何提交代码 - Apache inlong
+title: 如何提交代码 - Apache TubeMQ
---
# 如何提交代码
-Apache inlong使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
+Apache TubeMQ使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
-- inlong代码库：https://github.com/apache/incubator-inlong
+- TubeMQ代码库：https://github.com/apache/incubator-tubemq
-- inlong官网库：https://github.com/apache/incubator-inlong-website
+- TubeMQ官网库：https://github.com/apache/incubator-tubemq-website
## 1. Fork仓库
-进入 [apache/incubator-inlong](https://github.com/apache/incubator-inlong) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
+进入 [apache/incubator-tubemq](https://github.com/apache/incubator-tubemq) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
@@ -19,22 +19,22 @@ Apache inlong使用Github的Pull Request (PR)来接收贡献的代码，本文
### 2.1 将代码克隆到本地
```shell
-git clone https://github.com/<your_github_name>/incubator-inlong.git
+git clone https://github.com/<your_github_name>/incubator-tubemq.git
```
clone完成后，origin会默认指向github上的远程fork地址。
-### 2.2 将 apache/incubator-inlong 添加为本地仓库的远程分支upstream
+### 2.2 将 apache/incubator-tubemq 添加为本地仓库的远程分支upstream
```shell
-cd incubator-inlong
-git remote add upstream https://github.com/apache/incubator-inlong.git
+cd incubator-tubemq
+git remote add upstream https://github.com/apache/incubator-tubemq.git
```
### 2.3 检查远程仓库设置
```shell
git remote -v
-origin https://github.com/<your_github_name>/incubator-inlong.git (fetch)
-origin https://github.com/<your_github_name>/incubator-inlong.git(push)
-upstream https://github.com/apache/incubator-inlong.git (fetch)
-upstream https://github.com/apache/incubator-inlong.git (push)
+origin https://github.com/<your_github_name>/incubator-tubemq.git (fetch)
+origin https://github.com/<your_github_name>/incubator-tubemq.git(push)
+upstream https://github.com/apache/incubator-tubemq.git (fetch)
+upstream https://github.com/apache/incubator-tubemq.git (push)
```
此时会有两个仓库：origin(自己的仓库)和upstream（官方的仓库）
@@ -44,25 +44,25 @@ git fetch upstream
git pull upstream master
```
### 2.5 新建分支
-> 一般以issue id作为分支名，如：inlong-123
+> 一般以issue id作为分支名，如：TUBEMQ-123
```shell
-git checkout -b inlong-123
+git checkout -b TUBEMQ-123
```
-**确保分支`inlong-123`是基于官方master分支的最新代码**
+**确保分支`TUBEMQ-123`是基于官方master分支的最新代码**
分支创建完成后即可进行代码更改。
### 2.6 提交代码到远程分支
-> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[inlong-123] xxx`
+> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[TUBEMQ-123] xxx`
```shell
-git commit -a -m "[inlong-123] xxx"
-git push origin inlong-123
+git commit -a -m "[TUBEMQ-123] xxx"
+git push origin TUBEMQ-123
```
## 3. 创建PR
### 3.1 打开自己的github仓库页面
- `https://github.com/<your_github_name>/incubator-inlong`
+ `https://github.com/<your_github_name>/incubator-tubemq`
### 3.2. 切换分支
- 切换到提交的分支 `inlong-123`
+ 切换到提交的分支 `TUBEMQ-123`
### 3.3. 创建新PR
点击 `New pull request`或者`Compare & pull request`
@@ -70,7 +70,7 @@ git push origin inlong-123
需要注意以下几点：
1. PR的标题必须以issue id开头，最好与commit信息保持一致
2. 可以填写部分描述信息也可以不填
- 3. 如果点击`Create pull request`后提示代码冲突，则请将`inlong-123`分支的代码
+ 3. 如果点击`Create pull request`后提示代码冲突，则请将`TUBEMQ-123`分支的代码
与master分支同步一致后在进行提交
@@ -79,4 +79,4 @@ git push origin inlong-123
创建完PR后，所有的人都可以Review代码，可能会与您讨论一些实现的细节，可能还需要你进一步修改。
**一般该PR必须有2位以上的社区PPMC/Committer +1后，才可能正式合入官方代码库。**
-最后，恭喜您已经成为了inlong的官方贡献者了！
+最后，恭喜您已经成为了TubeMQ的官方贡献者了！
diff --git a/docs/zh-cn/development/how-to-contribute.md b/docs/zh-cn/development/how-to-contribute.md
index a03600e..8f16d2d 100644
--- a/docs/zh-cn/development/how-to-contribute.md
+++ b/docs/zh-cn/development/how-to-contribute.md
@@ -1,34 +1,34 @@
---
-title: 如何参与贡献 - Apache inlong
+title: 如何参与贡献 - Apache TubeMQ
---
# 如何参与贡献
-Apache inlong社区欢迎大家为Apache inlong做贡献，您可以通过很多方式为inlong项目成长贡献一份力量：
- - 贡献文档：浏览文档可以加深您对inlong的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:dev@inlong.apache.org)
- - 贡献代码：欢迎大家为inlong社区贡献代码
- - 欢迎您认领Open状态的[Issues](https://issues.apache.org/jira/projects/inlong/issues)和未完成的特性，提交PR，成为贡献者之一
+Apache TubeMQ社区欢迎大家为Apache TubeMQ做贡献，您可以通过很多方式为TubeMQ项目成长贡献一份力量：
+ - 贡献文档：浏览文档可以加深您对TubeMQ的了解，一旦发现文档写得不清晰或逻辑混乱的地方，可以订正、修改、补充或[联系我们](mailto:dev@tubemq.apache.org)
+ - 贡献代码：欢迎大家为TubeMQ社区贡献代码
+ - 欢迎您认领Open状态的[Issues](https://issues.apache.org/jira/projects/TUBEMQ/issues)和未完成的特性，提交PR，成为贡献者之一
- 如果您在使用过程中发现有些功能无法满足您的需求或出现问题，请在Issues中记录
- 参与邮件讨论：您可以参与dev邮件列表的任何讨论，或者发送任何疑问到dev邮件列表
- - 参与Issue讨论：您可以在任一[Issues](https://issues.apache.org/jira/projects/inlong/issues)下发表您的建议
- - Review代码：您可以在[GitHub](https://github.com/apache/incubator-inlong/pulls)上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议
+ - 参与Issue讨论：您可以在任一[Issues](https://issues.apache.org/jira/projects/TUBEMQ/issues)下发表您的建议
+ - Review代码：您可以在[GitHub](https://github.com/apache/incubator-tubemq/pulls)上看到所有贡献者提交的PR，您可以Review他们的代码并发表您的建议
> 欢迎大家提交Bug反馈、改进、新功能及PR，具体参与贡献流程可参考该指引。
## 1. 主要链接
-- 官网：https://inlong.apache.org/
-- 代码库：https://github.com/apache/incubator-inlong
-- 官网代码库：https://github.com/apache/incubator-inlong-website
-- JRIA任务管理：https://issues.apache.org/jira/projects/inlong/issues
+- 官网：https://tubemq.apache.org/
+- 代码库：https://github.com/apache/incubator-tubemq
+- 官网代码库：https://github.com/apache/incubator-tubemq-website
+- JRIA任务管理：https://issues.apache.org/jira/projects/TUBEMQ/issues
-## 2. 订阅inlong邮件列表
+## 2. 订阅TubeMQ邮件列表
详见[如何订阅邮件列表](how-to-subscribe.md)
## 3. 注册Jira账号
-Apache inlong使用Apache官方提供的任务管理平台对inlong相关的任务进行管理，JIRA的使用详见[JIRA使用指南](how-to-use-jira.md)
+Apache TUBEMQ使用Apache官方提供的任务管理平台对TubeMQ相关的任务进行管理，JIRA的使用详见[JIRA使用指南](how-to-use-jira.md)
## 4. 提交Bug反馈/特性/改进/文档
-> Apache inlong使用Apache官方提供的任务管理平台对inlong相关的任务进行管理，详见：https://issues.apache.org/jira/projects/inlong/issues
+> Apache TUBEMQ使用Apache官方提供的任务管理平台对TubeMQ相关的任务进行管理，详见：https://issues.apache.org/jira/projects/TUBEMQ/issues
### 4.1 创建issue
详见[JIRA使用指南](how-to-use-jira.md)
@@ -47,9 +47,9 @@ Apache inlong使用Apache官方提供的任务管理平台对inlong相关的任
- 编码，编码完成后，提交代码，参考：[代码提交指南](how-to-commit.md)
### 4.3 如何贡献文档
-inlong项目的所有文档将在[官网](https://inlong.apache.org/)展示，所有的文档都保存在官网代码库的[docs](https://github.com/apache/incubator-inlong-website/tree/master/docs)文件夹下。
+TubeMQ项目的所有文档将在[官网](https://tubemq.apache.org/)展示，所有的文档都保存在官网代码库的[docs](https://github.com/apache/incubator-tubemq-website/tree/master/docs)文件夹下。
贡献的文档包括：
-- 编写与inlong相关的文档
+- 编写与TubeMQ相关的文档
- 将中文文档翻译成英文文档
- 将英文文档翻译成中文文档
@@ -60,12 +60,12 @@ inlong项目的所有文档将在[官网](https://inlong.apache.org/)展示，
### 5. 如何认领Bug/特性/改进/文档
-在inlong的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：
+在TubeMQ的issue列表中，有很多由其他人创建的issue并未被修复，如果你感兴趣的话，可以认领这些issue。认领步骤如下：
- 在该issue下留言，表达想认领该任务的想法
- 如果提交者没有意见，则将该issue assign到自己名下并及时更新进度
- 如果是比较大的特性，尽量先输出设计文档，供其他人review
- 开发代码并提交代码至github，提交代码流程参考：[代码提交指南](how-to-commit.md)
-**如果你是第一次参与inlong项目，可能该issue无法Assign给自己，此时你可以发邮件至：dev@inlong.apache.org或联系inlong的PPMC申请加入inlong的contributor列表，加入后即可Assign其他issue给自己**
+**如果你是第一次参与TubeMQ项目，可能该issue无法Assign给自己，此时你可以发邮件至：dev@tubemq.apache.org或联系TubeMQ的PPMC申请加入TubeMQ的contributor列表，加入后即可Assign其他issue给自己**
-您的任何贡献都可以帮助Apache inlong项目成长，如果您刚接触inlong，您可以先从简单的任务入手，循序渐进，甚至可以逐渐成长为Apache inlong的Committer；
\ No newline at end of file
+您的任何贡献都可以帮助Apache TubeMQ项目成长，如果您刚接触TubeMQ，您可以先从简单的任务入手，循序渐进，甚至可以逐渐成长为Apache TubeMQ的Committer；
\ No newline at end of file
diff --git a/docs/zh-cn/development/how-to-release.md b/docs/zh-cn/development/how-to-release.md
index 2cc622b..d9cd57e 100644
--- a/docs/zh-cn/development/how-to-release.md
+++ b/docs/zh-cn/development/how-to-release.md
@@ -1,5 +1,5 @@
---
-title: 如何发布版本- Apache inlong
+title: 如何发布版本- Apache TubeMQ
---
# 如何发布版本
@@ -7,7 +7,7 @@ title: 如何发布版本- Apache inlong
> 本文主要介绍了Release Manager如何按照Apache的流程发布版本，
Source Release是Apache关注的重点，也是发布的必须内容；
-Binary Release是可选项，inlong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
+Binary Release是可选项，TubeMQ可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
请参考以下链接，找到更多关于ASF的发布指南:
@@ -122,29 +122,29 @@ http://keys.gnupg.net
> 这个步骤需要使用SVN
-DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/inlong
+Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/tubemq
#### 1.5.1 在dev分支中添加公钥到KEYS，用于发布RC版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
# 这个步骤比较慢，会把所有版本都拷贝下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-➜ ~ cd inlong-dist-dev
-➜ inlong-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ cd tubemq-dist-dev
+➜ tubemq-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
#### 1.5.2 在release分支中添加公钥到KEYS，用于发布正式版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/inlong /tmp/inlong-dist-release
-➜ ~ cd inlong-dist-release
-➜ inlong-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/tubemq /tmp/tubemq-dist-release
+➜ ~ cd tubemq-dist-release
+➜ tubemq-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
### 1.6 上传GPG公钥到Github账户
@@ -220,20 +220,20 @@ $ git config user.signingkey ${KEY_ID}
> tag创建成功后，我需要将tag源码打包成一个tar包
```shell
-mkdir /tmp/apache-inlong-${release_version}-${rc_version}
-git archive --format=tar.gz --output="/tmp/apache-inlong-${release_version}-${rc_version}/apache-inlong-${release_version}-src.tar.gz" --prefix="apache-inlong-${release_version}/" $git_tag
+mkdir /tmp/apache-tubemq-${release_version}-${rc_version}
+git archive --format=tar.gz --output="/tmp/apache-tubemq-${release_version}-${rc_version}/apache-tubemq-${release_version}-src.tar.gz" --prefix="apache-tubemq-${release_version}/" $git_tag
```
### 3.4 打包二进制包
> 编译上一步打包的源码
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version} # 进入源码目录
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version} # 进入源码目录
mvn compile clean install package -DskipTests # 编译
-cp ./inlong-client/target/apache-inlong-client-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
-cp ./inlong-server/target/apache-inlong-server-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-client/target/apache-tubemq-client-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-server/target/apache-tubemq-server-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
```
### 3.5 对源码包/二进制包进行签名/sha512
@@ -251,9 +251,9 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
## 4. 准备Apache发布
### 4.1 发布jar包到Apache Nexus仓库
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version}
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version}
mvn -DskipTests deploy -Papache-release -Dmaven.javadoc.skip=true # 开始上传
```
@@ -264,20 +264,20 @@ git push origin ${release_version}-${rc_version}
```
### 4.3 上传编译好的文件到dist
-> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-### 4.3.1 将inlong checkout到本地目录
+### 4.3.1 将TubeMQ checkout到本地目录
```shell
# 这个步骤可能会比较慢，会把所有版本都考下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
```
### 4.3.2 添加public key到KEYS文件并提交到SVN仓库
```shell
-cd /tmp/inlong-dist-dev
+cd /tmp/tubemq-dist-dev
mkdir ${release_version}-${rc_version} #创建版本目录
# 将源码包和签名包拷贝到此处
-cp /tmp/apache-inlong-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
+cp /tmp/apache-tubemq-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
svn status # 检查svn状态
svn add ${release_version}-${rc_version} # 添加到svn版本
svn status # 检查svn状态
@@ -287,62 +287,62 @@ svn commit -m 'prepare for ${release_version} ${rc_version}'# 提交至svn远程
> 请确保所有的artifact都是ok的
1. **先登录**http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库
4. 点击上方的Close按钮，这个过程会进行一系列检查
5. 检查通过以后, 在下方的Summary标签页上出现一个连接，请保存好这个链接，需要放在接下来的投票邮件当中。
-链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapacheinlong-xxxx`
+链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapachetubemq-xxxx`
WARN: 请注意点击Close可能会出现失败，请检查失败原因并处理
## 5. 进入投票
-> inlong仍旧在孵化中，需要进行两次投票，
-- inlong社区投票，发邮件至：`dev@inlong.apache.org`
+> TubeMQ仍旧在孵化中，需要进行两次投票，
+- TubeMQ社区投票，发邮件至：`dev@tubemq.apache.org`
- incubator社区投票，发邮件至：`general@incubator.apache.org`
-inlong毕业之后，只需要在inlong社区投票
+TubeMQ毕业之后，只需要在TubeMQ社区投票
-### 5.1 inlong社区投票
+### 5.1 TubeMQ社区投票
#### 5.1.1 投票模板
```html
-标题：[VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
- This is a call for vote to release Apache inlong version ${release_version}-${rc_version}.
+ This is a call for vote to release Apache TubeMQ version ${release_version}-${rc_version}.
The tag to be voted on is ${release_version}-${rc_version}:
- https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
The release tarball, signature, and checksums can be found at:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Maven artifacts are available in a staging repository at:
- https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}
+ https://repository.apache.org/content/repositories/orgapachetubemq-{staging-id}
Artifacts were signed with the {YOUR_PUB_KEY} key which can be found in:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
${release_version} includes ~ ${issue_count} bug and improvement fixes done since last versions which can be found at:
- https://github.com/apache/incubator-inlong/blob/${release_version}-${rc_version}/CHANGES.md
+ https://github.com/apache/incubator-tubemq/blob/${release_version}-${rc_version}/CHANGES.md
Please download, verify, and test.
The VOTE will remain open for at least 72 hours.
- [ ] +1 Release this package as Apache inlong ${release_version}
+ [ ] +1 Release this package as Apache TubeMQ ${release_version}
[ ] +0
[ ] -1 Do not release this package because...
- To learn more about apache inlong, please see
- http://inlong.apache.org/
+ To learn more about apache tubemq, please see
+ http://tubemq.apache.org/
Checklist for reference:
@@ -358,16 +358,16 @@ Hello Apache inlong PPMC and Community,
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Thanks,
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
#### 5.1.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
xx (+1 non-binding) votes from the PPMC,
@@ -381,7 +381,7 @@ Hello Apache inlong PPMC and Community,
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
### 5.2 incubator社区投票
@@ -389,38 +389,38 @@ Your inlong Release Manager
#### 5.2.1 投票模板
```html
-标题：[VOTE] Release Apache inlong (Incubating) ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ (Incubating) ${release_version} ${rc_version}
内容：
Hello Incubator Community,
- This is a call for a vote to release Apache inlong (Incubating) version
+ This is a call for a vote to release Apache TubeMQ (Incubating) version
${release_version} ${rc_version}
- The Apache inlong community has voted on and approved a proposal to release
- Apache inlong (Incubating) version ${release_version} ${rc_version}
+ The Apache TubeMQ community has voted on and approved a proposal to release
+ Apache TubeMQ (Incubating) version ${release_version} ${rc_version}
We now kindly request the Incubator PMC members review and vote on this
incubator release.
- inlong community vote thread:
+ TubeMQ community vote thread:
• [投票链接]
Vote result thread:
• [投票结果链接]
The release candidate:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Git tag for the release:
- • https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
Release notes:
- • https://github.com/apache/incubator-inlong/releases/tag/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/releases/tag/${release_version}-${rc_version}
The artifacts signed with PGP key [填写你个人的KEY], corresponding to [填写你个人的邮箱], that can be found in keys file:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
The vote will be open for at least 72 hours or until necessary number of votes are reached.
@@ -431,18 +431,18 @@ Hello Incubator Community,
[ ] -1 disapprove with the reason
Thanks,
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
#### 5.2.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} {rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} {rc_version}
内容：
Hi all
-Thanks for reviewing and voting for Apache inlong (Incubating) ${release_version} {rc_version}
+Thanks for reviewing and voting for Apache TubeMQ (Incubating) ${release_version} {rc_version}
release, I am happy to announce the release voting has passed with [投票结果数]
binding votes, no +0 or -1 votes. Binding votes are from IPMC
@@ -454,11 +454,11 @@ The voting thread is:
[投票链接]
Many thanks for all our mentors helping us with the release procedure, and
-all IPMC helped us to review and vote for Apache inlong (Incubating) release. I will
+all IPMC helped us to review and vote for Apache TubeMQ (Incubating) release. I will
be working on publishing the artifacts soon.
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
## 6. 正式发布
@@ -466,51 +466,51 @@ On behalf of Apache inlong (Incubating) community
### 6.1 合并release-${release_version}分支的改动到master分支
### 6.2 将源码和二进制包从svn的dev目录移动到release目录
```shell
-svn mv https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/inlong/${release_version} -m "Release ${release_version}"
+svn mv https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/tubemq/${release_version} -m "Release ${release_version}"
```
### 6.3 确认dev和release下的包是否正确
-1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/inlong/)下的`${release_version}-${rc_version}`已被删除
-2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/inlong/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/inlong/)
+1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/tubemq/)下的`${release_version}-${rc_version}`已被删除
+2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/tubemq/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/tubemq/)
```shell
-svn delete https://dist.apache.org/repos/dist/release/incubator/inlong/${last_release_version} -m "Delete ${last_release_version}"
+svn delete https://dist.apache.org/repos/dist/release/incubator/tubemq/${last_release_version} -m "Delete ${last_release_version}"
```
### 6.4 在Apache Staging仓库发布版本
> 请确保所有的artifact都是ok的
1. 登录http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库，投票邮件中指定的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库，投票邮件中指定的仓库
4. 点击上方的`Release`按钮，这个过程会进行一系列检查
**等仓库同步到其他数据源，一般需要24小时**
### 6.5 更新官网链接
-### 6.6. 发邮件到 `dev@inlong.apache.org` 和 `general@incubator.apache.org`
+### 6.6. 发邮件到 `dev@tubemq.apache.org` 和 `general@incubator.apache.org`
**请确保6.4中的仓库已发布成功，一般是在6.4后的24小时后发布邮件**
宣布release邮件模板：
```html
-标题： [ANNOUNCE] Release Apache inlong(incubating) ${release_version}
+标题： [ANNOUNCE] Release Apache TubeMQ(incubating) ${release_version}
内容：
Hi all,
-The Apache inlong(incubating) community is pleased to announce
-that Apache inlong (incubating) ${release_version} has been released!
+The Apache TubeMQ(incubating) community is pleased to announce
+that Apache TubeMQ (incubating) ${release_version} has been released!
-Apache inlong is a trillion-records-scale distributed messaging queue (MQ) system,
+Apache TubeMQ is a trillion-records-scale distributed messaging queue (MQ) system,
focuses on data transmission and storage under massive data.
Download Links: xxx
Release Notes: xxx
-Website: https://inlong.apache.org/
+Website: https://tubemq.apache.org/
-inlong Resources:
-- Issue: https://issues.apache.org/jira/projects/inlong/issues
-- Mailing list: dev@inlong.apache.org
+TubeMQ Resources:
+- Issue: https://issues.apache.org/jira/projects/TUBEMQ/issues
+- Mailing list: dev@tubemq.apache.org
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
diff --git a/docs/zh-cn/development/how-to-subscribe.md b/docs/zh-cn/development/how-to-subscribe.md
index c815c4e..7a246f9 100644
--- a/docs/zh-cn/development/how-to-subscribe.md
+++ b/docs/zh-cn/development/how-to-subscribe.md
@@ -1,35 +1,35 @@
---
-title: 订阅邮件列表 - Apache inlong
+title: 订阅邮件列表 - Apache TubeMQ
---
# 订阅邮件列表
邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
-订阅邮件后，你可以第一时间获取inlong社区的动态，可以与社区保持同步。
+订阅邮件后，你可以第一时间获取TubeMQ社区的动态，可以与社区保持同步。
-#### inlong项目邮件列表
+#### TubeMQ项目邮件列表
|名称|描述|订阅邮件|退订邮件|邮件归档|
|:-----|:--------|:------|:-------|:-----|
-| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@inlong.apache.org) | [退订](mailto:dev-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
-| [commits@inlong.apache.org](mailto:commits@inlong.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@inlong.apache.org) | [退订](mailto:commits-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
+| [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@tubemq.apache.org) | [退订](mailto:dev-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-dev) |
+| [commits@tubemq.apache.org](mailto:commits@tubemq.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@tubemq.apache.org) | [退订](mailto:commits-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-commits) |
## 1. 订阅邮件列表
-**以订阅dev@inlong.apache.org邮件列表为例**
+**以订阅dev@tubemq.apache.org邮件列表为例**
具体步骤如下：
- 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@inlong.apache.org`
- 2. 等待直到收到一封主题为 `confirm subscribe to dev@inlong.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
+ 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@tubemq.apache.org`
+ 2. 等待直到收到一封主题为 `confirm subscribe to dev@tubemq.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
3. 直接回复该邮件，不用修改主题和添加邮件内容。
- 4. 等待直到收到一封主题为 `WELCOME to dev@inlong.apache.org` 的邮件。
- 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@inlong.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
+ 4. 等待直到收到一封主题为 `WELCOME to dev@tubemq.apache.org` 的邮件。
+ 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@tubemq.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
## 2. 退订邮件列表
退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：
-1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@inlong.apache.org`
-2. 等待直到收到一封主题为 `confirm unsubscribe from dev@inlong.apache.org` 的邮件
+1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@tubemq.apache.org`
+2. 等待直到收到一封主题为 `confirm unsubscribe from dev@tubemq.apache.org` 的邮件
3. 直接回复该邮件，不用修改主题和添加邮件内容
-4. 等待直到收到一封主题为 `GOODBYE from dev@inlong.apache.org`的邮件
+4. 等待直到收到一封主题为 `GOODBYE from dev@tubemq.apache.org`的邮件
5. 退订成功
diff --git a/docs/zh-cn/development/how-to-use-jira.md b/docs/zh-cn/development/how-to-use-jira.md
index 50b1a75..b493906 100644
--- a/docs/zh-cn/development/how-to-use-jira.md
+++ b/docs/zh-cn/development/how-to-use-jira.md
@@ -1,21 +1,21 @@
---
-title: 如何使用JIRA - Apache inlong
+title: 如何使用JIRA - Apache TubeMQ
---
# JIRA使用指南
JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于
-项目的管理，基于此inlong项目同样使用JIRA来进行管理项目。本文将简单介绍在inlong的开发过程中如何使用JIRA。
+项目的管理，基于此TubeMQ项目同样使用JIRA来进行管理项目。本文将简单介绍在TubeMQ的开发过程中如何使用JIRA。
## 1. 注册并登陆到JIRA
对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：
1. 登录[注册](https://issues.apache.org/jira/secure/Signup!default.jspa)页面
2. 填入个人邮箱，姓名等注册信息后即可注册。
-3. 注册成功后登录并进入inlong项目。
+3. 注册成功后登录并进入TubeMQ项目。
## 2. 查看issues
-1. 打开[inlong](https://issues.apache.org/jira/projects/inlong/issues)项目页面
-2. 可以看到inlong项目的所有issue
+1. 打开[TubeMQ](https://issues.apache.org/jira/projects/TUBEMQ/issues)项目页面
+2. 可以看到TubeMQ项目的所有issue
3. 点击右上角`View all issues and filters`即可进行过滤issue，默认过滤规则包括任务类型、任务状态、负责人及输入关键字等搜索，
也点击右侧的`More`按钮，进行更多字段的过滤筛选。
@@ -26,7 +26,7 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
- 必填项
- - Project: Apache inlong
+ - Project: Apache TubeMQ
- Issue Type: 选择issue类型，包含：Task, Bug, Feature, Improvement等
- Summary: issue标题，一句话描述该issue所要表达的问题
- Reporter: issue的提交者，即本人
@@ -40,10 +40,10 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
创建好issue后可以将issue指定给自己或者其他人或者为空。如果指定给自己，此时你就可以准备开发代码解决该问题了。
-**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@inlong.apache.org或联系inlong的PPMC申请加入inlong的contributor列表，加入后即可Assign其他issue给自己**
+**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@tubemq.apache.org或联系TubeMQ的PPMC申请加入TubeMQ的contributor列表，加入后即可Assign其他issue给自己**
## 4. 关闭issues
-当该issue被解决后，可以关闭该issue，**一般由inlong的PPMC和Committer来关闭issue**。
+当该issue被解决后，可以关闭该issue，**一般由TubeMQ的PPMC和Committer来关闭issue**。
### 4.1. 点击`Resolve Issue`按钮
一般不要点击`Close Issue`，如下图所示：
diff --git a/docs/zh-cn/development/how-to-verify.md b/docs/zh-cn/development/how-to-verify.md
index 908bb06..bb26b29 100644
--- a/docs/zh-cn/development/how-to-verify.md
+++ b/docs/zh-cn/development/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: 如何验证版本- Apache inlong
+title: 如何验证版本- Apache TubeMQ
---
# 验证候选版本
@@ -8,7 +8,7 @@ title: 如何验证版本- Apache inlong
## 1. 下载要发布的候选版本到本地环境
```shell
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
```
## 2. 验证上传的版本是否合规
> 开始验证环节，验证包含但不局限于以下内容和形式
@@ -24,7 +24,7 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
### 2.2 检查gpg签名
- 导入公钥
```shell
- curl https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS > KEYS # 下载KEYS
+ curl https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS > KEYS # 下载KEYS
gpg --import KEYS # 导入KEYS到本地
```
- 信任公钥
@@ -85,15 +85,15 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
```shell
for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
#或者
- gpg --verify apache-inlong-${release_version}-src.tar.gz.asc apache-inlong-${release_version}-src.tar.gz
+ gpg --verify apache-tubemq-${release_version}-src.tar.gz.asc apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的签名是否正确
- gpg --verify apache-inlong-server-${release_version}-bin.tar.gz.asc apache-inlong-server-${release_version}-bin.tar.gz
- gpg --verify apache-inlong-client-${release_version}-bin.tar.gz.asc apache-inlong-client-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-server-${release_version}-bin.tar.gz.asc apache-tubemq-server-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-client-${release_version}-bin.tar.gz.asc apache-tubemq-client-${release_version}-bin.tar.gz
```
- 检查结果
> 出现类似以下内容则说明签名正确，关键字：**`Good signature`**
```shell
-apache-inlong-0.3.0-incubating-src.tar.gz
+apache-tubemq-0.3.0-incubating-src.tar.gz
gpg: Signature made Sat May 30 11:45:01 2020 CST
gpg: using RSA key 9B12C2228BDFF4F4CFE849445EF3A66D57EC647A
gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
@@ -104,17 +104,17 @@ gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
```shell
for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i; done
#或者
-gpg --print-md SHA512 apache-inlong-${release_version}-src.tar.gz
+gpg --print-md SHA512 apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的sha512哈希
-gpg --print-md SHA512 apache-inlong-server-${release_version}-bin.tar.gz
-gpg --print-md SHA512 apache-inlong-client-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-server-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-client-${release_version}-bin.tar.gz
# 或者
for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
```
### 2.4. 检查源码包的文件内容
- 解压缩`apache-inlong-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
@@ -124,8 +124,8 @@ for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
- ....
### 2.5 检查二进制包(如果上传了二进制包)
- 解压缩`apache-inlong-client-${release_version}-src.tar.gz`和`
- apache-inlong-server-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-client-${release_version}-src.tar.gz`和`
+ apache-tubemq-server-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
- 能否正常部署成功
diff --git a/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md b/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
index 2632f48..2f8eb6a 100644
--- a/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
+++ b/docs/zh-cn/development/how-to-vote-a-committer-ppmc.md
@@ -1,45 +1,45 @@
---
-title: 成为inlong Committer 或 PPMC 的投票过程 - Apache inlong
+title: 成为TubeMQ Committer 或 PPMC 的投票过程 - Apache TubeMQ
---
-# 成为inlong Committer 或 PPMC 的投票过程
+# 成为TubeMQ Committer 或 PPMC 的投票过程
-1. inlong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在inlong的private邮件列表发起讨论；
- > [DISCUSS] YYYYY as a inlong XXXXXX
+1. TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在TubeMQ的private邮件列表发起讨论；
+ > [DISCUSS] YYYYY as a TubeMQ XXXXXX
邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；
-2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在inlong的private邮件列表发起Committer或PPMC的选举投票；
- > [VOTE] YYYYY as a inlong XXXXXX
+2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在TubeMQ的private邮件列表发起Committer或PPMC的选举投票；
+ > [VOTE] YYYYY as a TubeMQ XXXXXX
投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1票则投票失败；如果-1，需要把问题说清楚，便于大家理解和知晓
3. 投票邮件结束后，由投票发起者在投票线上总结并提醒投票结束，并发投票总结邮件；
- > [RESULTS][VOTE] YYYYY as a inlong XXXXXX
+ > [RESULTS][VOTE] YYYYY as a TubeMQ XXXXXX
4. 投票总结邮件发出后，投票发起者要给候选人发起邀请邮件，该邀请邮件需要候选人通过指定的邮箱回复接受或者拒绝；
- > [Invitation] Invitation to join Apache inlong as a XXXXXX
+ > [Invitation] Invitation to join Apache TubeMQ as a XXXXXX
- 邮件主送邀请人，抄送private@inlong.apache.org
+ 邮件主送邀请人，抄送private@tubemq.apache.org
5. 候选人接受邀请后，如果候选人没有apache邮箱帐号，投票发起者需要协助候选人按照指引创建apache帐号；
6. 如果选举的是PPMC，在候选人的Apache帐号创建完成后，投票发起者还需要向IPMC的private邮件组发送知会邮件，并等待至少72小时;
- > [NOTICE] XXXXXX for inlong PPMC
+ > [NOTICE] XXXXXX for TubeMQ PPMC
- 邮件主送private@incubator.apache.org，抄送private@inlong.apache.org，IPMC们会分析合规性，直到没有疑义。
+ 邮件主送private@incubator.apache.org，抄送private@tubemq.apache.org，IPMC们会分析合规性，直到没有疑义。
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
- 7.2 向dev@inlong.apache.org邮件组发通知邮件：
+ 7.2 向dev@tubemq.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/docs/zh-cn/download/download.md b/docs/zh-cn/download/download.md
index ee1f9c1..40a2b9f 100644
--- a/docs/zh-cn/download/download.md
+++ b/docs/zh-cn/download/download.md
@@ -1,38 +1,38 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
## 下载链接
- 使用以下链接，下载inlong，最新版本为0.8.0.
+ 使用以下链接，下载TubeMQ，最新版本为0.8.0.
## 0.8.0 release
- 发布时间：2021-03-04
- [发版说明](release-0.8.0.md)
- - 源码: [inlong-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512)]
- - 客户端: [inlong-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512)]
- - 服务端: [inlong-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512)]
+ - 源码: [tubemq-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512)]
+ - 客户端: [tubemq-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512)]
+ - 服务端: [tubemq-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512)]
## 0.7.0 release
- 发布时间：2020-12-04
- [发版说明](release-0.7.0.md)
- - 源码: [inlong-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)]
- - 客户端: [inlong-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)]
- - 服务端: [inlong-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)]
+ - 源码: [tubemq-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)]
+ - 客户端: [tubemq-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)]
+ - 服务端: [tubemq-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)]
## 0.6.0 release
- 发布时间：2020-10-21
- [发版说明](release-0.6.0.md)
- - 源码: [inlong-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)]
- - 客户端: [inlong-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)]
- - 服务端: [inlong-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)]
+ - 源码: [tubemq-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)]
+ - 客户端: [tubemq-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)]
+ - 服务端: [tubemq-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)]
## 0.5.0 release
- 发布时间：2020-08-04
- [发版说明](release-0.5.0.md)
- - 源码: [inlong-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)]
- - 客户端: [inlong-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)]
- - 服务端: [inlong-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)]
+ - 源码: [tubemq-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)]
+ - 客户端: [tubemq-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)]
+ - 服务端: [tubemq-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)]
## 0.3.0 release
- 发布时间：2020-06-06
- [发版说明](release-0.3.0.md)
- - 源码: [inlong-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)]
- - 客户端: [inlong-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)]
- - 服务端: [inlong-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)]
+ - 源码: [tubemq-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)]
+ - 客户端: [tubemq-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)]
+ - 服务端: [tubemq-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)]
diff --git a/docs/zh-cn/download/release-0.3.0.md b/docs/zh-cn/download/release-0.3.0.md
index a4fcdf2..d29056b 100644
--- a/docs/zh-cn/download/release-0.3.0.md
+++ b/docs/zh-cn/download/release-0.3.0.md
@@ -1,64 +1,64 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
-# 下载inlong
- 使用以下镜像下载inlong
+# 下载TubeMQ
+ 使用以下镜像下载TubeMQ
-## inlong
+## TubeMQ
| 日期 | 版本| 备注 | 下载 |
|:---:|:--:|:--:|:--:|
-| 2020-06-06 | 0.3.0 | 源码 | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)] |
-| | | 客户端 | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)] |
-| | | 服务端 | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)] |
+| 2020-06-06 | 0.3.0 | 源码 | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)] |
+| | | 客户端 | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)] |
+| | | 服务端 | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)] |
## 发版说明
### 新特性
- - [[inlong-42](https://issues.apache.org/jira/browse/inlong-42)] Add peer information about message received Major New Feature
+ - [[TUBEMQ-42](https://issues.apache.org/jira/browse/TUBEMQ-42)] Add peer information about message received Major New Feature
### 改进
- - [[inlong-7](https://issues.apache.org/jira/browse/inlong-7)] Using StringBuilder instead of StringBuffer in BaseResult
- - [[inlong-9](https://issues.apache.org/jira/browse/inlong-9)] Remove some unnecessary code
- - [[inlong-16](https://issues.apache.org/jira/browse/inlong-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
- - [[inlong-18](https://issues.apache.org/jira/browse/inlong-18)] Correct TMaster#idGenerater to TMaster#idGenerator
- - [[inlong-19](https://issues.apache.org/jira/browse/inlong-19)] Correct parameter names to fit in camel case
- - [[inlong-20](https://issues.apache.org/jira/browse/inlong-20)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-21](https://issues.apache.org/jira/browse/inlong-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
- - [[inlong-22](https://issues.apache.org/jira/browse/inlong-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
- - [[inlong-23](https://issues.apache.org/jira/browse/inlong-23)] Improve project README content introduction
- - [[inlong-24](https://issues.apache.org/jira/browse/inlong-24)] Add NOTICE and adjust LICENSE
- - [[inlong-26](https://issues.apache.org/jira/browse/inlong-26)] correct spelling (difftime-> diffTime)
- - [[inlong-27](https://issues.apache.org/jira/browse/inlong-27)] replace StringBuffer with StringBuilder
- - [[inlong-28](https://issues.apache.org/jira/browse/inlong-28)] ignore path error
- - [[inlong-29](https://issues.apache.org/jira/browse/inlong-29)] Change the package name to org.apache.inlong.""
- - [[inlong-33](https://issues.apache.org/jira/browse/inlong-33)] refactor enum implement from annoymouse inner class
- - [[inlong-38](https://issues.apache.org/jira/browse/inlong-38)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-39](https://issues.apache.org/jira/browse/inlong-39)] Optimize the loadMessageStores() logic
- - [[inlong-40](https://issues.apache.org/jira/browse/inlong-40)] Optimize message disk store classes's logic
- - [[inlong-43](https://issues.apache.org/jira/browse/inlong-43)] Add DeletePolicy's value check
- - [[inlong-44](https://issues.apache.org/jira/browse/inlong-44)] Remove unnecessary synchronized definition of shutdown () function
- - [[inlong-49](https://issues.apache.org/jira/browse/inlong-49)] setTimeoutTime change to updTimeoutTime
- - [[inlong-50](https://issues.apache.org/jira/browse/inlong-50)] Replace fastjson to gson
+ - [[TUBEMQ-7](https://issues.apache.org/jira/browse/TUBEMQ-7)] Using StringBuilder instead of StringBuffer in BaseResult
+ - [[TUBEMQ-9](https://issues.apache.org/jira/browse/TUBEMQ-9)] Remove some unnecessary code
+ - [[TUBEMQ-16](https://issues.apache.org/jira/browse/TUBEMQ-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
+ - [[TUBEMQ-18](https://issues.apache.org/jira/browse/TUBEMQ-18)] Correct TMaster#idGenerater to TMaster#idGenerator
+ - [[TUBEMQ-19](https://issues.apache.org/jira/browse/TUBEMQ-19)] Correct parameter names to fit in camel case
+ - [[TUBEMQ-20](https://issues.apache.org/jira/browse/TUBEMQ-20)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-21](https://issues.apache.org/jira/browse/TUBEMQ-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
+ - [[TUBEMQ-22](https://issues.apache.org/jira/browse/TUBEMQ-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
+ - [[TUBEMQ-23](https://issues.apache.org/jira/browse/TUBEMQ-23)] Improve project README content introduction
+ - [[TUBEMQ-24](https://issues.apache.org/jira/browse/TUBEMQ-24)] Add NOTICE and adjust LICENSE
+ - [[TUBEMQ-26](https://issues.apache.org/jira/browse/TUBEMQ-26)] correct spelling (difftime-> diffTime)
+ - [[TUBEMQ-27](https://issues.apache.org/jira/browse/TUBEMQ-27)] replace StringBuffer with StringBuilder
+ - [[TUBEMQ-28](https://issues.apache.org/jira/browse/TUBEMQ-28)] ignore path error
+ - [[TUBEMQ-29](https://issues.apache.org/jira/browse/TUBEMQ-29)] Change the package name to org.apache.tubemq.""
+ - [[TUBEMQ-33](https://issues.apache.org/jira/browse/TUBEMQ-33)] refactor enum implement from annoymouse inner class
+ - [[TUBEMQ-38](https://issues.apache.org/jira/browse/TUBEMQ-38)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-39](https://issues.apache.org/jira/browse/TUBEMQ-39)] Optimize the loadMessageStores() logic
+ - [[TUBEMQ-40](https://issues.apache.org/jira/browse/TUBEMQ-40)] Optimize message disk store classes's logic
+ - [[TUBEMQ-43](https://issues.apache.org/jira/browse/TUBEMQ-43)] Add DeletePolicy's value check
+ - [[TUBEMQ-44](https://issues.apache.org/jira/browse/TUBEMQ-44)] Remove unnecessary synchronized definition of shutdown () function
+ - [[TUBEMQ-49](https://issues.apache.org/jira/browse/TUBEMQ-49)] setTimeoutTime change to updTimeoutTime
+ - [[TUBEMQ-50](https://issues.apache.org/jira/browse/TUBEMQ-50)] Replace fastjson to gson
### Bug修复
- - [[inlong-10](https://issues.apache.org/jira/browse/inlong-10)] Fix Javadoc error
- - [[inlong-14](https://issues.apache.org/jira/browse/inlong-14)] Some compilation errors
- - [[inlong-15](https://issues.apache.org/jira/browse/inlong-15)] Correct typo in http_access_API_definition.md
- - [[inlong-32](https://issues.apache.org/jira/browse/inlong-32)] File path not match with package name in inlong-client module
- - [[inlong-35](https://issues.apache.org/jira/browse/inlong-35)] check illegal package's field value
- - [[inlong-36](https://issues.apache.org/jira/browse/inlong-36)] Remove unnecessary removefirst() function printing
- - [[inlong-37](https://issues.apache.org/jira/browse/inlong-37)] Offset is set to 0 when Broker goes offline
- - [[inlong-45](https://issues.apache.org/jira/browse/inlong-45)] Check groupName with checkHostName function
- - [[inlong-48](https://issues.apache.org/jira/browse/inlong-48)] No timeout when setting consumer timeout
- - [[inlong-59](https://issues.apache.org/jira/browse/inlong-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
- - [[inlong-62](https://issues.apache.org/jira/browse/inlong-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
- - [[inlong-66](https://issues.apache.org/jira/browse/inlong-66)] TubeSingleSessionFactory shutdown bug
- - [[inlong-85](https://issues.apache.org/jira/browse/inlong-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
- - [[inlong-88](https://issues.apache.org/jira/browse/inlong-88)] Broker does not take effect after the deletePolicy value is changed
- - [[inlong-149](https://issues.apache.org/jira/browse/inlong-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-153](https://issues.apache.org/jira/browse/inlong-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-10](https://issues.apache.org/jira/browse/TUBEMQ-10)] Fix Javadoc error
+ - [[TUBEMQ-14](https://issues.apache.org/jira/browse/TUBEMQ-14)] Some compilation errors
+ - [[TUBEMQ-15](https://issues.apache.org/jira/browse/TUBEMQ-15)] Correct typo in http_access_API_definition.md
+ - [[TUBEMQ-32](https://issues.apache.org/jira/browse/TUBEMQ-32)] File path not match with package name in tubemq-client module
+ - [[TUBEMQ-35](https://issues.apache.org/jira/browse/TUBEMQ-35)] check illegal package's field value
+ - [[TUBEMQ-36](https://issues.apache.org/jira/browse/TUBEMQ-36)] Remove unnecessary removefirst() function printing
+ - [[TUBEMQ-37](https://issues.apache.org/jira/browse/TUBEMQ-37)] Offset is set to 0 when Broker goes offline
+ - [[TUBEMQ-45](https://issues.apache.org/jira/browse/TUBEMQ-45)] Check groupName with checkHostName function
+ - [[TUBEMQ-48](https://issues.apache.org/jira/browse/TUBEMQ-48)] No timeout when setting consumer timeout
+ - [[TUBEMQ-59](https://issues.apache.org/jira/browse/TUBEMQ-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
+ - [[TUBEMQ-62](https://issues.apache.org/jira/browse/TUBEMQ-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
+ - [[TUBEMQ-66](https://issues.apache.org/jira/browse/TUBEMQ-66)] TubeSingleSessionFactory shutdown bug
+ - [[TUBEMQ-85](https://issues.apache.org/jira/browse/TUBEMQ-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
+ - [[TUBEMQ-88](https://issues.apache.org/jira/browse/TUBEMQ-88)] Broker does not take effect after the deletePolicy value is changed
+ - [[TUBEMQ-149](https://issues.apache.org/jira/browse/TUBEMQ-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-153](https://issues.apache.org/jira/browse/TUBEMQ-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
diff --git a/docs/zh-cn/download/release-0.5.0.md b/docs/zh-cn/download/release-0.5.0.md
index cd7d0e8..0d16ee4 100644
--- a/docs/zh-cn/download/release-0.5.0.md
+++ b/docs/zh-cn/download/release-0.5.0.md
@@ -1,102 +1,102 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
-# 下载inlong
- 使用以下镜像下载inlong
+# 下载TubeMQ
+ 使用以下镜像下载TubeMQ
-## inlong
+## TubeMQ
| 日期 | 版本| 备注 | 下载 |
|:---:|:--:|:--:|:--:|
-| 2020-08-04 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)] |
+| 2020-08-04 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)] |
## 发版说明
### 新特性
- - [[inlong-122](https://issues.apache.org/jira/browse/inlong-122)] Increase JAVA version collection of SDK environment
- - [[inlong-163](https://issues.apache.org/jira/browse/inlong-163)] Flume sink for inlong
- - [[inlong-197](https://issues.apache.org/jira/browse/inlong-197)] Support inlong connector for Apache Flink
- - [[inlong-238](https://issues.apache.org/jira/browse/inlong-238)] Support inlong connector for Apache Spark Streaming
- - [[inlong-239](https://issues.apache.org/jira/browse/inlong-239)] support deployment on kubernetes
+ - [[TUBEMQ-122](https://issues.apache.org/jira/browse/TUBEMQ-122)] Increase JAVA version collection of SDK environment
+ - [[TUBEMQ-163](https://issues.apache.org/jira/browse/TUBEMQ-163)] Flume sink for TubeMQ
+ - [[TUBEMQ-197](https://issues.apache.org/jira/browse/TUBEMQ-197)] Support TubeMQ connector for Apache Flink
+ - [[TUBEMQ-238](https://issues.apache.org/jira/browse/TUBEMQ-238)] Support TubeMQ connector for Apache Spark Streaming
+ - [[TUBEMQ-239](https://issues.apache.org/jira/browse/TUBEMQ-239)] support deployment on kubernetes
### 改进
- - [[inlong-46](https://issues.apache.org/jira/browse/inlong-46)] Correct some spelling issues
- - [[inlong-53](https://issues.apache.org/jira/browse/inlong-53)] fix some typos
- - [[inlong-55](https://issues.apache.org/jira/browse/inlong-55)] fix some typos
- - [[inlong-57](https://issues.apache.org/jira/browse/inlong-57)] fix some typos
- - [[inlong-58](https://issues.apache.org/jira/browse/inlong-58)] fix some typos
- - [[inlong-60](https://issues.apache.org/jira/browse/inlong-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
- - [[inlong-61](https://issues.apache.org/jira/browse/inlong-61)] minor update & fix some typos
- - [[inlong-64](https://issues.apache.org/jira/browse/inlong-64)] minor update & fix some typos
- - [[inlong-67](https://issues.apache.org/jira/browse/inlong-67)] remove synchronized & fix some typos
- - [[inlong-71](https://issues.apache.org/jira/browse/inlong-71)] using IllegalArgumentException & fix some typos
- - [[inlong-73](https://issues.apache.org/jira/browse/inlong-73)] remove duplicate codes & some minor updates
- - [[inlong-74](https://issues.apache.org/jira/browse/inlong-74)] minor updates for DefaultBdbStoreService
- - [[inlong-75](https://issues.apache.org/jira/browse/inlong-75)] remove unused Logger
- - [[inlong-76](https://issues.apache.org/jira/browse/inlong-76)] rename the classes
- - [[inlong-77](https://issues.apache.org/jira/browse/inlong-77)] fix typo
- - [[inlong-79](https://issues.apache.org/jira/browse/inlong-79)] fix typo
- - [[inlong-80](https://issues.apache.org/jira/browse/inlong-80)] Fix some typos
- - [[inlong-82](https://issues.apache.org/jira/browse/inlong-82)] Fix some typos & update comments
- - [[inlong-83](https://issues.apache.org/jira/browse/inlong-83)] Fix some typos
- - [[inlong-87](https://issues.apache.org/jira/browse/inlong-87)] Minor updates
- - [[inlong-89](https://issues.apache.org/jira/browse/inlong-89)] Minor updates
- - [[inlong-90](https://issues.apache.org/jira/browse/inlong-90)] Remove unused codes in TubeBroker
- - [[inlong-91](https://issues.apache.org/jira/browse/inlong-91)] replace explicit type with <>
- - [[inlong-93](https://issues.apache.org/jira/browse/inlong-93)] Substitute the parameterized type for client module & missed server module
- - [[inlong-94](https://issues.apache.org/jira/browse/inlong-94)] Substitute the parameterized type for core module
- - [[inlong-95](https://issues.apache.org/jira/browse/inlong-95)] Substitute the parameterized type for server module
- - [[inlong-96](https://issues.apache.org/jira/browse/inlong-96)] Fix typo & use IllegalArgumentException
- - [[inlong-98](https://issues.apache.org/jira/browse/inlong-98)] Fix typo & Simplify 'instanceof' judgment
- - [[inlong-100](https://issues.apache.org/jira/browse/inlong-100)] Fix typos & remove unused codes
- - [[inlong-101](https://issues.apache.org/jira/browse/inlong-101)] Optimize code & Fix type
- - [[inlong-103](https://issues.apache.org/jira/browse/inlong-103)] Substitute Chinese comments with English
- - [[inlong-108](https://issues.apache.org/jira/browse/inlong-108)] About maven jdk version configuration problem
- - [[inlong-127](https://issues.apache.org/jira/browse/inlong-127)] Fixed a bug & minor changes
- - [[inlong-128](https://issues.apache.org/jira/browse/inlong-128)] Shorten the log clearup check cycle
- - [[inlong-138](https://issues.apache.org/jira/browse/inlong-138)] Optimize core module test case code
- - [[inlong-141](https://issues.apache.org/jira/browse/inlong-141)] Remove the requirement to provide localHostIP
- - [[inlong-152](https://issues.apache.org/jira/browse/inlong-152)] Modify the master.ini file's annotations
- - [[inlong-154](https://issues.apache.org/jira/browse/inlong-154)] Modify the wrong comment & Minor changes for example module
- - [[inlong-155](https://issues.apache.org/jira/browse/inlong-155)] Use enum class for consume position
- - [[inlong-156](https://issues.apache.org/jira/browse/inlong-156)] Update for README.md
- - [[inlong-166](https://issues.apache.org/jira/browse/inlong-166)] Hide `bdbStore` configs in master.ini
- - [[inlong-167](https://issues.apache.org/jira/browse/inlong-167)] Change to relative paths in default configs
- - [[inlong-168](https://issues.apache.org/jira/browse/inlong-168)] Example module: remove localhost IP configuration parameters
- - [[inlong-170](https://issues.apache.org/jira/browse/inlong-170)] improve build/deployment/configuration for quick start
- - [[inlong-196](https://issues.apache.org/jira/browse/inlong-196)] use log to print exception
- - [[inlong-201](https://issues.apache.org/jira/browse/inlong-201)] [Website] Adjust user guide & fix demo example
- - [[inlong-202](https://issues.apache.org/jira/browse/inlong-202)] Add protobuf protocol syntax declaration
- - [[inlong-213](https://issues.apache.org/jira/browse/inlong-213)] Optimize code & Minor changes
- - [[inlong-216](https://issues.apache.org/jira/browse/inlong-216)] use ThreadUtil.sleep replace Thread.sleep
- - [[inlong-222](https://issues.apache.org/jira/browse/inlong-222)] Optimize code: Unnecessary boxing/unboxing conversion
- - [[inlong-224](https://issues.apache.org/jira/browse/inlong-224)] Fixed: Unnecessary conversion to string inspection for server module
- - [[inlong-226](https://issues.apache.org/jira/browse/inlong-226)] Add Windows startup scripts
- - [[inlong-227](https://issues.apache.org/jira/browse/inlong-227)] remove build guide in docker-build readme
- - [[inlong-232](https://issues.apache.org/jira/browse/inlong-232)] TubeBroker#register2Master, reconnect and wait
- - [[inlong-234](https://issues.apache.org/jira/browse/inlong-234)] Add .asf.yaml to change notifications
- - [[inlong-235](https://issues.apache.org/jira/browse/inlong-235)] Add code coverage supporting for pull request created.
- - [[inlong-237](https://issues.apache.org/jira/browse/inlong-237)] add maven module build for docker image
+ - [[TUBEMQ-46](https://issues.apache.org/jira/browse/TUBEMQ-46)] Correct some spelling issues
+ - [[TUBEMQ-53](https://issues.apache.org/jira/browse/TUBEMQ-53)] fix some typos
+ - [[TUBEMQ-55](https://issues.apache.org/jira/browse/TUBEMQ-55)] fix some typos
+ - [[TUBEMQ-57](https://issues.apache.org/jira/browse/TUBEMQ-57)] fix some typos
+ - [[TUBEMQ-58](https://issues.apache.org/jira/browse/TUBEMQ-58)] fix some typos
+ - [[TUBEMQ-60](https://issues.apache.org/jira/browse/TUBEMQ-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
+ - [[TUBEMQ-61](https://issues.apache.org/jira/browse/TUBEMQ-61)] minor update & fix some typos
+ - [[TUBEMQ-64](https://issues.apache.org/jira/browse/TUBEMQ-64)] minor update & fix some typos
+ - [[TUBEMQ-67](https://issues.apache.org/jira/browse/TUBEMQ-67)] remove synchronized & fix some typos
+ - [[TUBEMQ-71](https://issues.apache.org/jira/browse/TUBEMQ-71)] using IllegalArgumentException & fix some typos
+ - [[TUBEMQ-73](https://issues.apache.org/jira/browse/TUBEMQ-73)] remove duplicate codes & some minor updates
+ - [[TUBEMQ-74](https://issues.apache.org/jira/browse/TUBEMQ-74)] minor updates for DefaultBdbStoreService
+ - [[TUBEMQ-75](https://issues.apache.org/jira/browse/TUBEMQ-75)] remove unused Logger
+ - [[TUBEMQ-76](https://issues.apache.org/jira/browse/TUBEMQ-76)] rename the classes
+ - [[TUBEMQ-77](https://issues.apache.org/jira/browse/TUBEMQ-77)] fix typo
+ - [[TUBEMQ-79](https://issues.apache.org/jira/browse/TUBEMQ-79)] fix typo
+ - [[TUBEMQ-80](https://issues.apache.org/jira/browse/TUBEMQ-80)] Fix some typos
+ - [[TUBEMQ-82](https://issues.apache.org/jira/browse/TUBEMQ-82)] Fix some typos & update comments
+ - [[TUBEMQ-83](https://issues.apache.org/jira/browse/TUBEMQ-83)] Fix some typos
+ - [[TUBEMQ-87](https://issues.apache.org/jira/browse/TUBEMQ-87)] Minor updates
+ - [[TUBEMQ-89](https://issues.apache.org/jira/browse/TUBEMQ-89)] Minor updates
+ - [[TUBEMQ-90](https://issues.apache.org/jira/browse/TUBEMQ-90)] Remove unused codes in TubeBroker
+ - [[TUBEMQ-91](https://issues.apache.org/jira/browse/TUBEMQ-91)] replace explicit type with <>
+ - [[TUBEMQ-93](https://issues.apache.org/jira/browse/TUBEMQ-93)] Substitute the parameterized type for client module & missed server module
+ - [[TUBEMQ-94](https://issues.apache.org/jira/browse/TUBEMQ-94)] Substitute the parameterized type for core module
+ - [[TUBEMQ-95](https://issues.apache.org/jira/browse/TUBEMQ-95)] Substitute the parameterized type for server module
+ - [[TUBEMQ-96](https://issues.apache.org/jira/browse/TUBEMQ-96)] Fix typo & use IllegalArgumentException
+ - [[TUBEMQ-98](https://issues.apache.org/jira/browse/TUBEMQ-98)] Fix typo & Simplify 'instanceof' judgment
+ - [[TUBEMQ-100](https://issues.apache.org/jira/browse/TUBEMQ-100)] Fix typos & remove unused codes
+ - [[TUBEMQ-101](https://issues.apache.org/jira/browse/TUBEMQ-101)] Optimize code & Fix type
+ - [[TUBEMQ-103](https://issues.apache.org/jira/browse/TUBEMQ-103)] Substitute Chinese comments with English
+ - [[TUBEMQ-108](https://issues.apache.org/jira/browse/TUBEMQ-108)] About maven jdk version configuration problem
+ - [[TUBEMQ-127](https://issues.apache.org/jira/browse/TUBEMQ-127)] Fixed a bug & minor changes
+ - [[TUBEMQ-128](https://issues.apache.org/jira/browse/TUBEMQ-128)] Shorten the log clearup check cycle
+ - [[TUBEMQ-138](https://issues.apache.org/jira/browse/TUBEMQ-138)] Optimize core module test case code
+ - [[TUBEMQ-141](https://issues.apache.org/jira/browse/TUBEMQ-141)] Remove the requirement to provide localHostIP
+ - [[TUBEMQ-152](https://issues.apache.org/jira/browse/TUBEMQ-152)] Modify the master.ini file's annotations
+ - [[TUBEMQ-154](https://issues.apache.org/jira/browse/TUBEMQ-154)] Modify the wrong comment & Minor changes for example module
+ - [[TUBEMQ-155](https://issues.apache.org/jira/browse/TUBEMQ-155)] Use enum class for consume position
+ - [[TUBEMQ-156](https://issues.apache.org/jira/browse/TUBEMQ-156)] Update for README.md
+ - [[TUBEMQ-166](https://issues.apache.org/jira/browse/TUBEMQ-166)] Hide `bdbStore` configs in master.ini
+ - [[TUBEMQ-167](https://issues.apache.org/jira/browse/TUBEMQ-167)] Change to relative paths in default configs
+ - [[TUBEMQ-168](https://issues.apache.org/jira/browse/TUBEMQ-168)] Example module: remove localhost IP configuration parameters
+ - [[TUBEMQ-170](https://issues.apache.org/jira/browse/TUBEMQ-170)] improve build/deployment/configuration for quick start
+ - [[TUBEMQ-196](https://issues.apache.org/jira/browse/TUBEMQ-196)] use log to print exception
+ - [[TUBEMQ-201](https://issues.apache.org/jira/browse/TUBEMQ-201)] [Website] Adjust user guide & fix demo example
+ - [[TUBEMQ-202](https://issues.apache.org/jira/browse/TUBEMQ-202)] Add protobuf protocol syntax declaration
+ - [[TUBEMQ-213](https://issues.apache.org/jira/browse/TUBEMQ-213)] Optimize code & Minor changes
+ - [[TUBEMQ-216](https://issues.apache.org/jira/browse/TUBEMQ-216)] use ThreadUtil.sleep replace Thread.sleep
+ - [[TUBEMQ-222](https://issues.apache.org/jira/browse/TUBEMQ-222)] Optimize code: Unnecessary boxing/unboxing conversion
+ - [[TUBEMQ-224](https://issues.apache.org/jira/browse/TUBEMQ-224)] Fixed: Unnecessary conversion to string inspection for server module
+ - [[TUBEMQ-226](https://issues.apache.org/jira/browse/TUBEMQ-226)] Add Windows startup scripts
+ - [[TUBEMQ-227](https://issues.apache.org/jira/browse/TUBEMQ-227)] remove build guide in docker-build readme
+ - [[TUBEMQ-232](https://issues.apache.org/jira/browse/TUBEMQ-232)] TubeBroker#register2Master, reconnect and wait
+ - [[TUBEMQ-234](https://issues.apache.org/jira/browse/TUBEMQ-234)] Add .asf.yaml to change notifications
+ - [[TUBEMQ-235](https://issues.apache.org/jira/browse/TUBEMQ-235)] Add code coverage supporting for pull request created.
+ - [[TUBEMQ-237](https://issues.apache.org/jira/browse/TUBEMQ-237)] add maven module build for docker image
### Bug修复
- - [[inlong-47](https://issues.apache.org/jira/browse/inlong-47)] Fix some typos
- - [[inlong-102](https://issues.apache.org/jira/browse/inlong-102)] Fix question [inlong-101] [Optimize code]
- - [[inlong-121](https://issues.apache.org/jira/browse/inlong-121)] Fix compilation alarm
- - [[inlong-139](https://issues.apache.org/jira/browse/inlong-139)] a bug in the equals method of the TubeClientConfig class
- - [[inlong-157](https://issues.apache.org/jira/browse/inlong-157)] Optimize Broker disk anomaly check
- - [[inlong-158](https://issues.apache.org/jira/browse/inlong-158)] nextWithAuthInfo2B status should be managed independently according to Broker
- - [[inlong-159](https://issues.apache.org/jira/browse/inlong-159)] Fix some typos
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
- - [[inlong-205](https://issues.apache.org/jira/browse/inlong-205)] Duplicate dependency of jetty in tuber-server pom file
- - [[inlong-206](https://issues.apache.org/jira/browse/inlong-206)] There are some residual files after executed unit tests
- - [[inlong-210](https://issues.apache.org/jira/browse/inlong-210)] Add log4j properties file for unit tests
- - [[inlong-217](https://issues.apache.org/jira/browse/inlong-217)] UPdate the je download path
- - [[inlong-218](https://issues.apache.org/jira/browse/inlong-218)] build failed: Too many files with unapproved license
- - [[inlong-230](https://issues.apache.org/jira/browse/inlong-230)] inlong run mvn test failed with openjdk version 13.0.2
- - [[inlong-236](https://issues.apache.org/jira/browse/inlong-236)] Can't get dependencies from the maven repository
- - [[inlong-253](https://issues.apache.org/jira/browse/inlong-253)] tube-consumer fetch-worker cpu used too high
- - [[inlong-254](https://issues.apache.org/jira/browse/inlong-254)] support using different mapping port for standalone mode
- - [[inlong-265](https://issues.apache.org/jira/browse/inlong-265)] Unexpected broker disappearance in broker list after updating default broker metadata
+ - [[TUBEMQ-47](https://issues.apache.org/jira/browse/TUBEMQ-47)] Fix some typos
+ - [[TUBEMQ-102](https://issues.apache.org/jira/browse/TUBEMQ-102)] Fix question [TUBEMQ-101] [Optimize code]
+ - [[TUBEMQ-121](https://issues.apache.org/jira/browse/TUBEMQ-121)] Fix compilation alarm
+ - [[TUBEMQ-139](https://issues.apache.org/jira/browse/TUBEMQ-139)] a bug in the equals method of the TubeClientConfig class
+ - [[TUBEMQ-157](https://issues.apache.org/jira/browse/TUBEMQ-157)] Optimize Broker disk anomaly check
+ - [[TUBEMQ-158](https://issues.apache.org/jira/browse/TUBEMQ-158)] nextWithAuthInfo2B status should be managed independently according to Broker
+ - [[TUBEMQ-159](https://issues.apache.org/jira/browse/TUBEMQ-159)] Fix some typos
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-205](https://issues.apache.org/jira/browse/TUBEMQ-205)] Duplicate dependency of jetty in tuber-server pom file
+ - [[TUBEMQ-206](https://issues.apache.org/jira/browse/TUBEMQ-206)] There are some residual files after executed unit tests
+ - [[TUBEMQ-210](https://issues.apache.org/jira/browse/TUBEMQ-210)] Add log4j properties file for unit tests
+ - [[TUBEMQ-217](https://issues.apache.org/jira/browse/TUBEMQ-217)] UPdate the je download path
+ - [[TUBEMQ-218](https://issues.apache.org/jira/browse/TUBEMQ-218)] build failed: Too many files with unapproved license
+ - [[TUBEMQ-230](https://issues.apache.org/jira/browse/TUBEMQ-230)] TubeMQ run mvn test failed with openjdk version 13.0.2
+ - [[TUBEMQ-236](https://issues.apache.org/jira/browse/TUBEMQ-236)] Can't get dependencies from the maven repository
+ - [[TUBEMQ-253](https://issues.apache.org/jira/browse/TUBEMQ-253)] tube-consumer fetch-worker cpu used too high
+ - [[TUBEMQ-254](https://issues.apache.org/jira/browse/TUBEMQ-254)] support using different mapping port for standalone mode
+ - [[TUBEMQ-265](https://issues.apache.org/jira/browse/TUBEMQ-265)] Unexpected broker disappearance in broker list after updating default broker metadata
diff --git a/docs/zh-cn/download/release-0.6.0.md b/docs/zh-cn/download/release-0.6.0.md
index 4dbbbff..3e9daf7 100644
--- a/docs/zh-cn/download/release-0.6.0.md
+++ b/docs/zh-cn/download/release-0.6.0.md
@@ -1,38 +1,38 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
-# 下载inlong
- 使用以下镜像下载inlong
+# 下载TubeMQ
+ 使用以下镜像下载TubeMQ
-## inlong
+## TubeMQ
| 日期 | 版本| 备注 | 下载 |
|:---:|:--:|:--:|:--:|
-| 2020-10-21 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)] |
+| 2020-10-21 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)] |
## 发版说明
### 新特性
-- [[inlong-319](https://issues.apache.org/jira/browse/inlong-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
-- [[inlong-3](https://issues.apache.org/jira/browse/inlong-3)] C++ SDK support in inlong
+- [[TUBEMQ-319](https://issues.apache.org/jira/browse/TUBEMQ-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
+- [[TUBEMQ-3](https://issues.apache.org/jira/browse/TUBEMQ-3)] C++ SDK support in TubeMQ
### 改进
-- [[inlong-311](https://issues.apache.org/jira/browse/inlong-311)] Feedback more production information
-- [[inlong-312](https://issues.apache.org/jira/browse/inlong-312)] Feedback more consumption information
-- [[inlong-325](https://issues.apache.org/jira/browse/inlong-325)] Add 406 ~ 408 error code to pullSelect call
-- [[inlong-345](https://issues.apache.org/jira/browse/inlong-345)] Optimize the call logic of getMessage() in Pull mode
-- [[inlong-352](https://issues.apache.org/jira/browse/inlong-352)] Set the parameters of the example at startup
-- [[inlong-353](https://issues.apache.org/jira/browse/inlong-353)] Update LICENSE about C/C++ SDK's code reference
-- [[inlong-356](https://issues.apache.org/jira/browse/inlong-356)] C++ SDK Codec decode add requestid
-- [[inlong-327](https://issues.apache.org/jira/browse/inlong-327)] Fix the concurrency problem in the example
+- [[TUBEMQ-311](https://issues.apache.org/jira/browse/TUBEMQ-311)] Feedback more production information
+- [[TUBEMQ-312](https://issues.apache.org/jira/browse/TUBEMQ-312)] Feedback more consumption information
+- [[TUBEMQ-325](https://issues.apache.org/jira/browse/TUBEMQ-325)] Add 406 ~ 408 error code to pullSelect call
+- [[TUBEMQ-345](https://issues.apache.org/jira/browse/TUBEMQ-345)] Optimize the call logic of getMessage() in Pull mode
+- [[TUBEMQ-352](https://issues.apache.org/jira/browse/TUBEMQ-352)] Set the parameters of the example at startup
+- [[TUBEMQ-353](https://issues.apache.org/jira/browse/TUBEMQ-353)] Update LICENSE about C/C++ SDK's code reference
+- [[TUBEMQ-356](https://issues.apache.org/jira/browse/TUBEMQ-356)] C++ SDK Codec decode add requestid
+- [[TUBEMQ-327](https://issues.apache.org/jira/browse/TUBEMQ-327)] Fix the concurrency problem in the example
### BUG修复
-- [[inlong-316](https://issues.apache.org/jira/browse/inlong-316)] Where the port the port is aleady used, the process throw the exception, but not exit
-- [[inlong-317](https://issues.apache.org/jira/browse/inlong-317)] The Store Manager throws java.lang.NullPointerException
-- [[inlong-320](https://issues.apache.org/jira/browse/inlong-320)] Request for static web contents would get responses with no content
-- [[inlong-354](https://issues.apache.org/jira/browse/inlong-354)] Found a dns translate bug in C/C++ sdk
-- [[inlong-306](https://issues.apache.org/jira/browse/inlong-306)] Raise Nullpointer Exception when create inlong instance
-- [[inlong-359](https://issues.apache.org/jira/browse/inlong-359)] inlong consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
+- [[TUBEMQ-316](https://issues.apache.org/jira/browse/TUBEMQ-316)] Where the port the port is aleady used, the process throw the exception, but not exit
+- [[TUBEMQ-317](https://issues.apache.org/jira/browse/TUBEMQ-317)] The Store Manager throws java.lang.NullPointerException
+- [[TUBEMQ-320](https://issues.apache.org/jira/browse/TUBEMQ-320)] Request for static web contents would get responses with no content
+- [[TUBEMQ-354](https://issues.apache.org/jira/browse/TUBEMQ-354)] Found a dns translate bug in C/C++ sdk
+- [[TUBEMQ-306](https://issues.apache.org/jira/browse/TUBEMQ-306)] Raise Nullpointer Exception when create tubemq instance
+- [[TUBEMQ-359](https://issues.apache.org/jira/browse/TUBEMQ-359)] TubeMQ consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
diff --git a/docs/zh-cn/download/release-0.7.0.md b/docs/zh-cn/download/release-0.7.0.md
index 29e1548..f556381 100644
--- a/docs/zh-cn/download/release-0.7.0.md
+++ b/docs/zh-cn/download/release-0.7.0.md
@@ -1,51 +1,51 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
-# 下载inlong
- 使用以下镜像下载inlong
+# 下载TubeMQ
+ 使用以下镜像下载TubeMQ
-## inlong
+## TubeMQ
| 日期 | 版本| 备注 | 下载 |
|:---:|:--:|:--:|:--:|
-| 2020-12-04 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)] |
+| 2020-12-04 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)] |
## 发版说明
### 新特性
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-162](https://issues.apache.org/jira/browse/inlong-162) | Python SDK support in inlong | High |
-| [inlong-336](https://issues.apache.org/jira/browse/inlong-336) | Propose web portal to manage tube cluster Phase-I | Major |
-| [inlong-390](https://issues.apache.org/jira/browse/inlong-390) | support build C++ SDK with docker image | Normal |
+| [TUBEMQ-162](https://issues.apache.org/jira/browse/TUBEMQ-162) | Python SDK support in TubeMQ | High |
+| [TUBEMQ-336](https://issues.apache.org/jira/browse/TUBEMQ-336) | Propose web portal to manage tube cluster Phase-I | Major |
+| [TUBEMQ-390](https://issues.apache.org/jira/browse/TUBEMQ-390) | support build C++ SDK with docker image | Normal |
### 改进
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-369](https://issues.apache.org/jira/browse/inlong-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
-| [inlong-373](https://issues.apache.org/jira/browse/inlong-373) | Reduce the redundant code of Utils::Split functions | Major |
-| [inlong-374](https://issues.apache.org/jira/browse/inlong-374) | Adjust some coding style issues | Major |
-| [inlong-375](https://issues.apache.org/jira/browse/inlong-375) | Add a section to the README file about how to compile the project| Major |
-| [inlong-385](https://issues.apache.org/jira/browse/inlong-385) | update docker images | Major |
-| [inlong-393](https://issues.apache.org/jira/browse/inlong-393) | Optimize the mapping code of WEB API | Major |
-| [inlong-406](https://issues.apache.org/jira/browse/inlong-406) | test_consumer.py works for both Python 2 and 3 | Minor |
-| [inlong-410](https://issues.apache.org/jira/browse/inlong-410) | install python package and simplify test_consumer.py | Major |
-| [inlong-416](https://issues.apache.org/jira/browse/inlong-416) | support consume from specified position | Major |
-| [inlong-417](https://issues.apache.org/jira/browse/inlong-417) | C++ Client support parse message from binary data for Python SDK | Major |
-| [inlong-419](https://issues.apache.org/jira/browse/inlong-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
+| [TUBEMQ-369](https://issues.apache.org/jira/browse/TUBEMQ-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
+| [TUBEMQ-373](https://issues.apache.org/jira/browse/TUBEMQ-373) | Reduce the redundant code of Utils::Split functions | Major |
+| [TUBEMQ-374](https://issues.apache.org/jira/browse/TUBEMQ-374) | Adjust some coding style issues | Major |
+| [TUBEMQ-375](https://issues.apache.org/jira/browse/TUBEMQ-375) | Add a section to the README file about how to compile the project| Major |
+| [TUBEMQ-385](https://issues.apache.org/jira/browse/TUBEMQ-385) | update docker images | Major |
+| [TUBEMQ-393](https://issues.apache.org/jira/browse/TUBEMQ-393) | Optimize the mapping code of WEB API | Major |
+| [TUBEMQ-406](https://issues.apache.org/jira/browse/TUBEMQ-406) | test_consumer.py works for both Python 2 and 3 | Minor |
+| [TUBEMQ-410](https://issues.apache.org/jira/browse/TUBEMQ-410) | install python package and simplify test_consumer.py | Major |
+| [TUBEMQ-416](https://issues.apache.org/jira/browse/TUBEMQ-416) | support consume from specified position | Major |
+| [TUBEMQ-417](https://issues.apache.org/jira/browse/TUBEMQ-417) | C++ Client support parse message from binary data for Python SDK | Major |
+| [TUBEMQ-419](https://issues.apache.org/jira/browse/TUBEMQ-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
### BUG修复
| JIRA | Summary | Priority |
| :----------------------------------------------------------- | :----------------------------------------------------------- | :------- |
-| [inlong-365](https://issues.apache.org/jira/browse/inlong-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
-| [inlong-370](https://issues.apache.org/jira/browse/inlong-370) | Calling GetCurConsumedInfo API always returns failure | Major |
-| [inlong-376](https://issues.apache.org/jira/browse/inlong-376) | Move pullrequests_status notifications commits mail list | Major |
-| [inlong-366](https://issues.apache.org/jira/browse/inlong-366) | Found a nullpointerexception bug in broker | Normal |
-| [inlong-379](https://issues.apache.org/jira/browse/inlong-379) | Modify the memory cache size default to 3M | Normal |
-| [inlong-380](https://issues.apache.org/jira/browse/inlong-380) | Cpp client link error when gcc optimization is disabled | Major |
-| [inlong-405](https://issues.apache.org/jira/browse/inlong-405) | python sdk install files lack of the whole cpp configuration | Major |
-| [inlong-401](https://issues.apache.org/jira/browse/inlong-401) | python sdk readme bug | Minor |
-| [inlong-407](https://issues.apache.org/jira/browse/inlong-407) | Fix some content in README.md | Trivial |
-| [inlong-418](https://issues.apache.org/jira/browse/inlong-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
+| [TUBEMQ-365](https://issues.apache.org/jira/browse/TUBEMQ-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
+| [TUBEMQ-370](https://issues.apache.org/jira/browse/TUBEMQ-370) | Calling GetCurConsumedInfo API always returns failure | Major |
+| [TUBEMQ-376](https://issues.apache.org/jira/browse/TUBEMQ-376) | Move pullrequests_status notifications commits mail list | Major |
+| [TUBEMQ-366](https://issues.apache.org/jira/browse/TUBEMQ-366) | Found a nullpointerexception bug in broker | Normal |
+| [TUBEMQ-379](https://issues.apache.org/jira/browse/TUBEMQ-379) | Modify the memory cache size default to 3M | Normal |
+| [TUBEMQ-380](https://issues.apache.org/jira/browse/TUBEMQ-380) | Cpp client link error when gcc optimization is disabled | Major |
+| [TUBEMQ-405](https://issues.apache.org/jira/browse/TUBEMQ-405) | python sdk install files lack of the whole cpp configuration | Major |
+| [TUBEMQ-401](https://issues.apache.org/jira/browse/TUBEMQ-401) | python sdk readme bug | Minor |
+| [TUBEMQ-407](https://issues.apache.org/jira/browse/TUBEMQ-407) | Fix some content in README.md | Trivial |
+| [TUBEMQ-418](https://issues.apache.org/jira/browse/TUBEMQ-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
diff --git a/docs/zh-cn/download/release-0.8.0.md b/docs/zh-cn/download/release-0.8.0.md
index 72779f5..1741972 100644
--- a/docs/zh-cn/download/release-0.8.0.md
+++ b/docs/zh-cn/download/release-0.8.0.md
@@ -1,100 +1,100 @@
---
-title: 下载 - Apache inlong
+title: 下载 - Apache TubeMQ
---
-# 下载inlong
- 使用以下镜像下载inlong
+# 下载TubeMQ
+ 使用以下镜像下载TubeMQ
-## inlong
+## TubeMQ
| 日期 | 版本| 备注 | 下载 |
|:---:|:--:|:--:|:--:|
-| 2021-03-04 | 0.8.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512)] |
+| 2021-03-04 | 0.8.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512)] |
## 发版说明
### 改进:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-430](https://issues.apache.org/jira/browse/inlong-430) | Optimizing the implementation of HTTP API for broke | Major |
-| [inlong-445](https://issues.apache.org/jira/browse/inlong-445) | Adjust the status check default sleep interval of pullConsumeReadyChkSliceMs | Major |
-| [inlong-448](https://issues.apache.org/jira/browse/inlong-448) | Add Committer and PPMC operation process | Major |
-| [inlong-449](https://issues.apache.org/jira/browse/inlong-449) | Adjust Example implementation | Major |
-| [inlong-452](https://issues.apache.org/jira/browse/inlong-452) | Optimize rebalance performance | Major |
-| [inlong-467](https://issues.apache.org/jira/browse/inlong-467) | Add WEB APIs of Master and Broker | Major |
-| [inlong-489](https://issues.apache.org/jira/browse/inlong-489) | Add the maximum message length parameter setting | Major |
-| [inlong-495](https://issues.apache.org/jira/browse/inlong-495) | Code implementation adjustment based on SpotBugs check | Major |
-| [inlong-511](https://issues.apache.org/jira/browse/inlong-511) | Replace the conditional operator (?:) with mid() | Major |
-| [inlong-512](https://issues.apache.org/jira/browse/inlong-512) | Add package length control based on Topic | Major |
-| [inlong-515](https://issues.apache.org/jira/browse/inlong-515) | Add cluster Topic view web api | Major |
+| [TUBEMQ-430](https://issues.apache.org/jira/browse/TUBEMQ-430) | Optimizing the implementation of HTTP API for broke | Major |
+| [TUBEMQ-445](https://issues.apache.org/jira/browse/TUBEMQ-445) | Adjust the status check default sleep interval of pullConsumeReadyChkSliceMs | Major |
+| [TUBEMQ-448](https://issues.apache.org/jira/browse/TUBEMQ-448) | Add Committer and PPMC operation process | Major |
+| [TUBEMQ-449](https://issues.apache.org/jira/browse/TUBEMQ-449) | Adjust Example implementation | Major |
+| [TUBEMQ-452](https://issues.apache.org/jira/browse/TUBEMQ-452) | Optimize rebalance performance | Major |
+| [TUBEMQ-467](https://issues.apache.org/jira/browse/TUBEMQ-467) | Add WEB APIs of Master and Broker | Major |
+| [TUBEMQ-489](https://issues.apache.org/jira/browse/TUBEMQ-489) | Add the maximum message length parameter setting | Major |
+| [TUBEMQ-495](https://issues.apache.org/jira/browse/TUBEMQ-495) | Code implementation adjustment based on SpotBugs check | Major |
+| [TUBEMQ-511](https://issues.apache.org/jira/browse/TUBEMQ-511) | Replace the conditional operator (?:) with mid() | Major |
+| [TUBEMQ-512](https://issues.apache.org/jira/browse/TUBEMQ-512) | Add package length control based on Topic | Major |
+| [TUBEMQ-515](https://issues.apache.org/jira/browse/TUBEMQ-515) | Add cluster Topic view web api | Major |
### BUG修复:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-437](https://issues.apache.org/jira/browse/inlong-437) | Fix inlong table source sink factory instance creating problem | Major |
-| [inlong-441](https://issues.apache.org/jira/browse/inlong-441) | An error occurred when using the inlong class to create a sink table | Major |
-| [inlong-442](https://issues.apache.org/jira/browse/inlong-442) | Modifying the jvm parameters when the broker starts does not take effect | Major |
-| [inlong-443](https://issues.apache.org/jira/browse/inlong-443) | inlongSourceFunction class prints too many logs problem | Major |
-| [inlong-446](https://issues.apache.org/jira/browse/inlong-446) | Small bugs fix that do not affect the main logics | Major |
-| [inlong-450](https://issues.apache.org/jira/browse/inlong-450) | TubeClientException: Generate producer id failed | Major |
-| [inlong-453](https://issues.apache.org/jira/browse/inlong-453) | inlongSourceFunction class prints too many logs problem | Major |
-| [inlong-506](https://issues.apache.org/jira/browse/inlong-506) | cmakelist error | Major |
-| [inlong-510](https://issues.apache.org/jira/browse/inlong-510) | Found a bug in MessageProducerExample class | Major |
-| [inlong-518](https://issues.apache.org/jira/browse/inlong-518) | fix parameter pass error | Major |
-| [inlong-526](https://issues.apache.org/jira/browse/inlong-526) | Adjust the packaging script and version check list, remove the "-WIP" tag | Major |
-| [inlong-555](https://issues.apache.org/jira/browse/inlong-555) | short session data can only be written to a specific partition | Major |
-| [inlong-556](https://issues.apache.org/jira/browse/inlong-556) | Index value is bigger than the actual number of records | Low |
+| [TUBEMQ-437](https://issues.apache.org/jira/browse/TUBEMQ-437) | Fix tubemq table source sink factory instance creating problem | Major |
+| [TUBEMQ-441](https://issues.apache.org/jira/browse/TUBEMQ-441) | An error occurred when using the Tubemq class to create a sink table | Major |
+| [TUBEMQ-442](https://issues.apache.org/jira/browse/TUBEMQ-442) | Modifying the jvm parameters when the broker starts does not take effect | Major |
+| [TUBEMQ-443](https://issues.apache.org/jira/browse/TUBEMQ-443) | TubemqSourceFunction class prints too many logs problem | Major |
+| [TUBEMQ-446](https://issues.apache.org/jira/browse/TUBEMQ-446) | Small bugs fix that do not affect the main logics | Major |
+| [TUBEMQ-450](https://issues.apache.org/jira/browse/TUBEMQ-450) | TubeClientException: Generate producer id failed | Major |
+| [TUBEMQ-453](https://issues.apache.org/jira/browse/TUBEMQ-453) | TubemqSourceFunction class prints too many logs problem | Major |
+| [TUBEMQ-506](https://issues.apache.org/jira/browse/TUBEMQ-506) | cmakelist error | Major |
+| [TUBEMQ-510](https://issues.apache.org/jira/browse/TUBEMQ-510) | Found a bug in MessageProducerExample class | Major |
+| [TUBEMQ-518](https://issues.apache.org/jira/browse/TUBEMQ-518) | fix parameter pass error | Major |
+| [TUBEMQ-526](https://issues.apache.org/jira/browse/TUBEMQ-526) | Adjust the packaging script and version check list, remove the "-WIP" tag | Major |
+| [TUBEMQ-555](https://issues.apache.org/jira/browse/TUBEMQ-555) | short session data can only be written to a specific partition | Major |
+| [TUBEMQ-556](https://issues.apache.org/jira/browse/TUBEMQ-556) | Index value is bigger than the actual number of records | Low |
### 任务:
| JIRA | Summary | Priority |
|:---- |:---- | :--- |
-| [inlong-505](https://issues.apache.org/jira/browse/inlong-505) | Remove the "WIP" label of the DISCLAIMER file | Major |
-| [inlong-543](https://issues.apache.org/jira/browse/inlong-543) | Modify the LICENSE statement of multiple files and others | Major |
-| [inlong-557](https://issues.apache.org/jira/browse/inlong-557) | Handle the issues mentioned in the 0.8.0-RC2 review | Major |
-| [inlong-562](https://issues.apache.org/jira/browse/inlong-562) | Update project contents according to the 0.8.0-RC3 review | Major |
+| [TUBEMQ-505](https://issues.apache.org/jira/browse/TUBEMQ-505) | Remove the "WIP" label of the DISCLAIMER file | Major |
+| [TUBEMQ-543](https://issues.apache.org/jira/browse/TUBEMQ-543) | Modify the LICENSE statement of multiple files and others | Major |
+| [TUBEMQ-557](https://issues.apache.org/jira/browse/TUBEMQ-557) | Handle the issues mentioned in the 0.8.0-RC2 review | Major |
+| [TUBEMQ-562](https://issues.apache.org/jira/browse/TUBEMQ-562) | Update project contents according to the 0.8.0-RC3 review | Major |
### 子任务:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-428](https://issues.apache.org/jira/browse/inlong-433) | Bumped version to 0.8.0-SNAPSHOT | Major |
-| [inlong-433](https://issues.apache.org/jira/browse/inlong-433) | add inlong perf-consumer/producer scripts | Major |
-| [inlong-434](https://issues.apache.org/jira/browse/inlong-434) | Adjust Broker API mapping | Major |
-| [inlong-435](https://issues.apache.org/jira/browse/inlong-435) | Create Web field Mapping | Major |
-| [inlong-436](https://issues.apache.org/jira/browse/inlong-436) | Adjust Broker's HTTP API implementation | Major |
-| [inlong-439](https://issues.apache.org/jira/browse/inlong-439) | Add Cli field Scheme definition | Major |
-| [inlong-440](https://issues.apache.org/jira/browse/inlong-440) | Add feature package tube-manager to zip | Major |
-| [inlong-444](https://issues.apache.org/jira/browse/inlong-444) | Add consume and produce Cli commands | Major |
-| [inlong-447](https://issues.apache.org/jira/browse/inlong-447) | Add Broker-Admin Cli | Major |
-| [inlong-451](https://issues.apache.org/jira/browse/inlong-451) | Replace ConsumeTupleInfo with Tuple2 | Major |
-| [inlong-457](https://issues.apache.org/jira/browse/inlong-457) | There is no need to return StringBuilder in Master.java | Major |
-| [inlong-463](https://issues.apache.org/jira/browse/inlong-463) | Adjust Master rebalance process implementation | Major |
-| [inlong-464](https://issues.apache.org/jira/browse/inlong-464) | Add parameter rebalanceParallel in master.ini | Major |
-| [inlong-470](https://issues.apache.org/jira/browse/inlong-470) | Add query API of TopicName and BrokerId collection | Major |
-| [inlong-471](https://issues.apache.org/jira/browse/inlong-471) | Add query API Introduction of TopicName and BrokerId collection | Major |
-| [inlong-472](https://issues.apache.org/jira/browse/inlong-472) | Adjust Broker's AbstractWebHandler class implementation | Major |
-| [inlong-475](https://issues.apache.org/jira/browse/inlong-475) | add the offset clone api of the consume group | Major |
-| [inlong-482](https://issues.apache.org/jira/browse/inlong-482) | Add offset query api | Major |
-| [inlong-484](https://issues.apache.org/jira/browse/inlong-484) | Add query API for topic publication information | Major |
-| [inlong-485](https://issues.apache.org/jira/browse/inlong-485) | Add the batch setting API of consume group offset | Major |
-| [inlong-486](https://issues.apache.org/jira/browse/inlong-486) | Add the delete API of consumer group offset | Major |
-| [inlong-494](https://issues.apache.org/jira/browse/inlong-494) | Update API interface instruction document | Major |
-| [inlong-499](https://issues.apache.org/jira/browse/inlong-499) | Add configure store | Major |
-| [inlong-500](https://issues.apache.org/jira/browse/inlong-500) | Add setting operate API | Major |
-| [inlong-501](https://issues.apache.org/jira/browse/inlong-501) | Adjust max message size check logic | Major |
-| [inlong-502](https://issues.apache.org/jira/browse/inlong-502) | Add setting API interface document | Major |
-| [inlong-504](https://issues.apache.org/jira/browse/inlong-504) | Adjust the WebMethodMapper class interfaces | Major |
-| [inlong-508](https://issues.apache.org/jira/browse/inlong-508) | Optimize Broker's PB parameter check processing logic | Major |
-| [inlong-509](https://issues.apache.org/jira/browse/inlong-509) | Adjust the packet length check when data is loaded | Major |
-| [inlong-522](https://issues.apache.org/jira/browse/inlong-522) | Add admin_query_cluster_topic_view API document | Major |
-| [inlong-544](https://issues.apache.org/jira/browse/inlong-544) | Adjust the LICENSE statement in the client.conf files of Python and C/C++ SDK | Major |
-| [inlong-546](https://issues.apache.org/jira/browse/inlong-546) | Restore the original license header of the referenced external source files | Major |
-| [inlong-547](https://issues.apache.org/jira/browse/inlong-547) | Recode the implementation of the *Startup.java classes in the Tool package | Major |
-| [inlong-548](https://issues.apache.org/jira/browse/inlong-548) | Handle the LICENSE authorization of font files in the resources | Major |
-| [inlong-549](https://issues.apache.org/jira/browse/inlong-549) | Handling the problem of compilation failure | Major |
-| [inlong-550](https://issues.apache.org/jira/browse/inlong-550) | Adjust LICENSE file content | Major |
-| [inlong-551](https://issues.apache.org/jira/browse/inlong-551) | Adjust NOTICE file content | Major |
-| [inlong-558](https://issues.apache.org/jira/browse/inlong-558) | Adjust the LICENSE of the file header | Major |
-| [inlong-559](https://issues.apache.org/jira/browse/inlong-559) | Update the LICENSE file according to the 0.8.0-RC2 review | Major |
-| [inlong-560](https://issues.apache.org/jira/browse/inlong-560) | Remove unprepared modules | Major |
+| [TUBEMQ-428](https://issues.apache.org/jira/browse/TUBEMQ-433) | Bumped version to 0.8.0-SNAPSHOT | Major |
+| [TUBEMQ-433](https://issues.apache.org/jira/browse/TUBEMQ-433) | add tubemq perf-consumer/producer scripts | Major |
+| [TUBEMQ-434](https://issues.apache.org/jira/browse/TUBEMQ-434) | Adjust Broker API mapping | Major |
+| [TUBEMQ-435](https://issues.apache.org/jira/browse/TUBEMQ-435) | Create Web field Mapping | Major |
+| [TUBEMQ-436](https://issues.apache.org/jira/browse/TUBEMQ-436) | Adjust Broker's HTTP API implementation | Major |
+| [TUBEMQ-439](https://issues.apache.org/jira/browse/TUBEMQ-439) | Add Cli field Scheme definition | Major |
+| [TUBEMQ-440](https://issues.apache.org/jira/browse/TUBEMQ-440) | Add feature package tube-manager to zip | Major |
+| [TUBEMQ-444](https://issues.apache.org/jira/browse/TUBEMQ-444) | Add consume and produce Cli commands | Major |
+| [TUBEMQ-447](https://issues.apache.org/jira/browse/TUBEMQ-447) | Add Broker-Admin Cli | Major |
+| [TUBEMQ-451](https://issues.apache.org/jira/browse/TUBEMQ-451) | Replace ConsumeTupleInfo with Tuple2 | Major |
+| [TUBEMQ-457](https://issues.apache.org/jira/browse/TUBEMQ-457) | There is no need to return StringBuilder in Master.java | Major |
+| [TUBEMQ-463](https://issues.apache.org/jira/browse/TUBEMQ-463) | Adjust Master rebalance process implementation | Major |
+| [TUBEMQ-464](https://issues.apache.org/jira/browse/TUBEMQ-464) | Add parameter rebalanceParallel in master.ini | Major |
+| [TUBEMQ-470](https://issues.apache.org/jira/browse/TUBEMQ-470) | Add query API of TopicName and BrokerId collection | Major |
+| [TUBEMQ-471](https://issues.apache.org/jira/browse/TUBEMQ-471) | Add query API Introduction of TopicName and BrokerId collection | Major |
+| [TUBEMQ-472](https://issues.apache.org/jira/browse/TUBEMQ-472) | Adjust Broker's AbstractWebHandler class implementation | Major |
+| [TUBEMQ-475](https://issues.apache.org/jira/browse/TUBEMQ-475) | add the offset clone api of the consume group | Major |
+| [TUBEMQ-482](https://issues.apache.org/jira/browse/TUBEMQ-482) | Add offset query api | Major |
+| [TUBEMQ-484](https://issues.apache.org/jira/browse/TUBEMQ-484) | Add query API for topic publication information | Major |
+| [TUBEMQ-485](https://issues.apache.org/jira/browse/TUBEMQ-485) | Add the batch setting API of consume group offset | Major |
+| [TUBEMQ-486](https://issues.apache.org/jira/browse/TUBEMQ-486) | Add the delete API of consumer group offset | Major |
+| [TUBEMQ-494](https://issues.apache.org/jira/browse/TUBEMQ-494) | Update API interface instruction document | Major |
+| [TUBEMQ-499](https://issues.apache.org/jira/browse/TUBEMQ-499) | Add configure store | Major |
+| [TUBEMQ-500](https://issues.apache.org/jira/browse/TUBEMQ-500) | Add setting operate API | Major |
+| [TUBEMQ-501](https://issues.apache.org/jira/browse/TUBEMQ-501) | Adjust max message size check logic | Major |
+| [TUBEMQ-502](https://issues.apache.org/jira/browse/TUBEMQ-502) | Add setting API interface document | Major |
+| [TUBEMQ-504](https://issues.apache.org/jira/browse/TUBEMQ-504) | Adjust the WebMethodMapper class interfaces | Major |
+| [TUBEMQ-508](https://issues.apache.org/jira/browse/TUBEMQ-508) | Optimize Broker's PB parameter check processing logic | Major |
+| [TUBEMQ-509](https://issues.apache.org/jira/browse/TUBEMQ-509) | Adjust the packet length check when data is loaded | Major |
+| [TUBEMQ-522](https://issues.apache.org/jira/browse/TUBEMQ-522) | Add admin_query_cluster_topic_view API document | Major |
+| [TUBEMQ-544](https://issues.apache.org/jira/browse/TUBEMQ-544) | Adjust the LICENSE statement in the client.conf files of Python and C/C++ SDK | Major |
+| [TUBEMQ-546](https://issues.apache.org/jira/browse/TUBEMQ-546) | Restore the original license header of the referenced external source files | Major |
+| [TUBEMQ-547](https://issues.apache.org/jira/browse/TUBEMQ-547) | Recode the implementation of the *Startup.java classes in the Tool package | Major |
+| [TUBEMQ-548](https://issues.apache.org/jira/browse/TUBEMQ-548) | Handle the LICENSE authorization of font files in the resources | Major |
+| [TUBEMQ-549](https://issues.apache.org/jira/browse/TUBEMQ-549) | Handling the problem of compilation failure | Major |
+| [TUBEMQ-550](https://issues.apache.org/jira/browse/TUBEMQ-550) | Adjust LICENSE file content | Major |
+| [TUBEMQ-551](https://issues.apache.org/jira/browse/TUBEMQ-551) | Adjust NOTICE file content | Major |
+| [TUBEMQ-558](https://issues.apache.org/jira/browse/TUBEMQ-558) | Adjust the LICENSE of the file header | Major |
+| [TUBEMQ-559](https://issues.apache.org/jira/browse/TUBEMQ-559) | Update the LICENSE file according to the 0.8.0-RC2 review | Major |
+| [TUBEMQ-560](https://issues.apache.org/jira/browse/TUBEMQ-560) | Remove unprepared modules | Major |
diff --git a/docs/zh-cn/error_code.md b/docs/zh-cn/error_code.md
index 7be3270..2fda460 100644
--- a/docs/zh-cn/error_code.md
+++ b/docs/zh-cn/error_code.md
@@ -1,10 +1,10 @@
---
-title: 错误码 - Apache inlong
+title: 错误码 - Apache TubeMQ
---
-# inlong错误信息介绍
+# TubeMQ错误信息介绍
- inlong采用的是 错误码(errCode) + 错误详情(errMsg) 相结合的方式返回具体的操作结果。首先根据错误码确定是哪类问题，然后根据错误详情来确定具体的错误原因。表格汇总了所有的错误码以及运行中大家可能遇到的错误详情的相关对照。
+ TubeMQ采用的是 错误码(errCode) + 错误详情(errMsg) 相结合的方式返回具体的操作结果。首先根据错误码确定是哪类问题，然后根据错误详情来确定具体的错误原因。表格汇总了所有的错误码以及运行中大家可能遇到的错误详情的相关对照。
## 错误码
diff --git a/docs/zh-cn/http_access_api.md b/docs/zh-cn/http_access_api.md
index 31b8c62..c70d4b9 100644
--- a/docs/zh-cn/http_access_api.md
+++ b/docs/zh-cn/http_access_api.md
@@ -1,5 +1,5 @@
---
-title: HTTP API介绍 - Apache inlong
+title: HTTP API介绍 - Apache TubeMQ
---
# HTTP API定义
@@ -15,7 +15,7 @@ HTTP API是Master或者Broker对外功能暴露的接口，管控台的各项操
由于接口众多且参数繁杂，md格式不能比较好的表达，因而以excel附件形式提供给到大家：
-<a href="appendixfiles/http_access_api_definition_cn.xls" target="_blank">inlong HTTP API</a>
+<a href="appendixfiles/http_access_api_definition_cn.xls" target="_blank">TubeMQ HTTP API</a>
---
<a href="#top">Back to top</a>
\ No newline at end of file
diff --git a/docs/zh-cn/producer_example.md b/docs/zh-cn/producer_example.md
index 78f050f..9d29451 100644
--- a/docs/zh-cn/producer_example.md
+++ b/docs/zh-cn/producer_example.md
@@ -1,9 +1,9 @@
---
-title: 生产者示例 - Apache inlong
+title: 生产者示例 - Apache TubeMQ
---
## Producer 示例
-inlong提供了两种方式来初始化 session factory: TubeSingleSessionFactory 和 TubeMultiSessionFactory。
+TubeMQ提供了两种方式来初始化 session factory: TubeSingleSessionFactory 和 TubeMultiSessionFactory。
- TubeSingleSessionFactory 在整个生命周期只会创建一个 session
- TubeMultiSessionFactory 每次调用都会创建一个session
diff --git a/docs/zh-cn/quick_start.md b/docs/zh-cn/quick_start.md
index 1925ff9..bd200a1 100644
--- a/docs/zh-cn/quick_start.md
+++ b/docs/zh-cn/quick_start.md
@@ -1,5 +1,5 @@
---
-title: 快速开始 - Apache inlong
+title: 快速开始 - Apache TubeMQ
---
## 编译和构建
@@ -14,7 +14,7 @@ mvn clean package -DskipTests
```
- （可选）使用Docker编译：
```bash
-docker run -v REPLACE_WITH_SOURCE_PATH:/inlong apacheinlong/inlong-build clean package -DskipTests
+docker run -v REPLACE_WITH_SOURCE_PATH:/tubemq apachetubemq/tubemq-build clean package -DskipTests
```
- 单元测试：
```bash
@@ -23,11 +23,11 @@ mvn test
- 单独对每个 module 进行构建：
```bash
mvn clean install
-cd module-name (比如: inlong-client)
+cd module-name (比如: tubemq-client)
mvn test
```
-构建完成之后，在 `inlong-server/target` 目录下会有 **inlong-server-[inlong-VERSION]-bin.tar.gz** 文件。
-这是 inlong 的部署包，包含了脚本、配置文件、依赖以及 web GUI相关的内容。
+构建完成之后，在 `tubemq-server/target` 目录下会有 **tubemq-server-[TUBEMQ-VERSION]-bin.tar.gz** 文件。
+这是 TubeMq 的部署包，包含了脚本、配置文件、依赖以及 web GUI相关的内容。
### 配置IDE开发环境
在IDE中构建和调试源码，需要先运行以下命令：
```bash
@@ -35,7 +35,7 @@ mvn compile
```
执行之后，会生成 `protoc` 文件对应的 java source file，位于 `target/generated-sources` 目录。
-（可选）如果你打算使用本地的 `protoc` 可执行文件，你可以修改 `inlong-core/pom.xml` 下的 `protobuf-maven-plugin` 的配置，如下所示。
+（可选）如果你打算使用本地的 `protoc` 可执行文件，你可以修改 `tubemq-core/pom.xml` 下的 `protobuf-maven-plugin` 的配置，如下所示。
```xml
<configuration>
<outputDirectory>${project.build.directory}/generated-sources/java</outputDirectory>
@@ -43,23 +43,23 @@ mvn compile
</configuration>
```
## 部署运行
-### 部署inlong Standalone
+### 部署TubeMQ Standalone
Standalone模式可以在一个容器中启动zookeeper/master/broker服务：
```
-docker run -p 8080:8080 -p 8000:8000 -p 8123:8123 --name inlong -d apacheinlong/inlong-all:latest
+docker run -p 8080:8080 -p 8000:8000 -p 8123:8123 --name tubemq -d apachetubemq/tubemq-all:latest
```
容器拉起后，可在浏览器访问` http://127.0.0.1:8080`，然后参考下面`快速使用`部分开始使用。
**注意**：Standalone模式只可用于开发和体验，不可作为生产集群。
-### 部署inlong集群
+### 部署TubeMQ集群
#### 准备工作
- ZooKeeper集群
-- [inlong-server-[inlong-VERSION]-bin.tar.gz](download/download.md)安装包
+- [tubemq-server-[TUBEMQ-VERSION]-bin.tar.gz](download/download.md)安装包
选择安装路径后，安装包解压后的目录结构如下：
```
-/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin/
+/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin/
├── bin
├── conf
├── lib
@@ -67,14 +67,14 @@ docker run -p 8080:8080 -p 8000:8000 -p 8123:8123 --name inlong -d apacheinlong/
└── resources
```
#### 配置示例
-inlong 集群包含有两个组件: **Master** 和 **Broker**. Master 和 Broker 可以部署在相同或者不同的节点上。下面是
+TubeMQ 集群包含有两个组件: **Master** 和 **Broker**. Master 和 Broker 可以部署在相同或者不同的节点上。下面是
一个集群的配置示例：
| Role | TCP Port | TLS Port | Web Port | Comment |
| ---- | -------- | -------- | -------- | ------- |
| Master | 8099 | 8199 | 8080 | 元数据存储在 /stage/metadata |
| Broker | 8123 | 8124 | 8081 | 消息存储在 /stage/msgdata |
-| Zookeeper | 2181 | | | Offset 存储在 /inlong |
+| Zookeeper | 2181 | | | Offset 存储在 /tubemq |
#### 配置Master
编辑`conf/master.ini`，根据集群信息变更以下配置项
@@ -92,20 +92,20 @@ confModAuthToken=abc // 该token用于页面配置、API调
- ZooKeeper集群地址
```ini
[zookeeper]
-zkNodeRoot=/inlong
+zkNodeRoot=/tubemq
zkServerAddr=localhost:2181 // 指向zookeeper集群，多个地址逗号分开
```
- 配置Replication策略
```ini
[replication]
-repNodeName=inlongMasterGroupNode1 // 每个master节点需使用不同名称
+repNodeName=tubemqMasterGroupNode1 // 每个master节点需使用不同名称
repHelperHost=FIRST_MASTER_NODE_IP:9001 // helperHost用于创建master集群，一般配置第一个master节点ip
```
- 前端安装路径
编辑resources/velocity.properties
```properties
-file.resource.loader.path=/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin/resources/templates
+file.resource.loader.path=/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin/resources/templates
```
- （可选）生产环境，多master HA级别
@@ -138,23 +138,23 @@ primaryPath=/stage/msgdata
- ZooKeeper集群地址
```ini
[zookeeper]
-zkNodeRoot=/inlong
+zkNodeRoot=/tubemq
zkServerAddr=localhost:2181 // 指向zookeeper集群，多个地址逗号分开
```
#### 启动Master
进入Master节点的 `bin` 目录下，启动服务:
```bash
-./inlong master start
+./tubemq master start
```
访问Master的管控台 `http://YOUR_MASTER_IP:8080` ，页面可查则表示master已成功启动:
-
+
#### 配置Broker元数据
Broker启动前，首先要在Master上配置Broker元数据，增加Broker相关的管理信息。在`Broker List` 页面, `Add Single Broker`，然后填写相关信息:
-
+
需要填写的内容包括：
1. broker IP: broker server ip
@@ -162,43 +162,43 @@ Broker启动前，首先要在Master上配置Broker元数据，增加Broker相
然后上线Broker：
-
+
#### 启动Broker
进入broker节点的 `bin` 目录下，执行以下命令启动Broker服务：
```bash
-./inlong broker start
+./tubemq broker start
```
刷新页面可以看到 Broker 已经注册，当 `当前运行子状态` 为 `idle` 时， 可以增加topic。
-
+
## 快速使用
### 新增 Topic
可以通过 web GUI 添加 Topic， 在 `Topic列表`页面添加，需要填写相关信息，比如增加`demo` topic：
-
+
然后选择部署 Topic 的 Broker
-
+
此时 Broker的 `可发布` 和 `可订阅` 依旧是灰色的
-
+
需要在 `Broker列表`页面重载Broker 配置
-
+
-
+
之后就可以在页面查看Topic信息。
-
+
### 运行Example
@@ -208,36 +208,36 @@ Broker启动前，首先要在Master上配置Broker元数据，增加Broker相
将 `YOUR_MASTER_IP` 替换为实际的IP，然后运行producer:
```bash
-install_path=/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin
+install_path=/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin
java -Dlog4j.configuration=file:${install_path}/conf/tools.log4j.properties \
-Djava.net.preferIPv4Stack=true -cp ${install_path}/lib/*:${install_path}/conf/* \
-org.apache.inlong.example.MessageProducerExample \
+org.apache.tubemq.example.MessageProducerExample \
YOUR_MASTER_IP:8000 demo 100000
```
如果能观察下如下日志，则表示数据发送成功：
```bash
-[2020-06-04 11:19:04,405] INFO Send demo 1000 message, keyCount is 252 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:04,652] INFO Send demo 2000 message, keyCount is 502 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:05,096] INFO Send demo 3000 message, keyCount is 752 (org.apache.inlong.example.MessageProducerExample)
-[2020-06-04 11:19:05,181] INFO Send demo 4000 message, keyCount is 1002 (org.apache.inlong.example.MessageProducerExample)
+[2020-06-04 11:19:04,405] INFO Send demo 1000 message, keyCount is 252 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:04,652] INFO Send demo 2000 message, keyCount is 502 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:05,096] INFO Send demo 3000 message, keyCount is 752 (org.apache.tubemq.example.MessageProducerExample)
+[2020-06-04 11:19:05,181] INFO Send demo 4000 message, keyCount is 1002 (org.apache.tubemq.example.MessageProducerExample)
```
- 消费消息
将 `YOUR_MASTER_IP` 替换为实际的IP，然后运行Consumer:
```bash
-install_path=/INSTALL_PATH/inlong-server-[inlong-VERSION]-bin
+install_path=/INSTALL_PATH/tubemq-server-[TUBEMQ-VERSION]-bin
java -Xmx512m -Dlog4j.configuration=file:${install_path}/conf/tools.log4j.properties \
-Djava.net.preferIPv4Stack=true -cp ${install_path}/lib/*:${install_path}/conf/* \
-org.apache.inlong.example.MessageConsumerExample \
+org.apache.tubemq.example.MessageConsumerExample \
YOUR_MASTER_IP:8000 demo demoGroup 3 1 1
```
如果能观察下如下日志，则表示数据被消费者消费到：
```bash
-[2020-06-04 11:20:29,107] INFO Receive messages:270000 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,206] INFO Receive messages:272500 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,590] INFO Receive messages:275000 (org.apache.inlong.example.MsgRecvStats)
-[2020-06-04 11:20:31,910] INFO Receive messages:277500 (org.apache.inlong.example.MsgRecvStats)
+[2020-06-04 11:20:29,107] INFO Receive messages:270000 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,206] INFO Receive messages:272500 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,590] INFO Receive messages:275000 (org.apache.tubemq.example.MsgRecvStats)
+[2020-06-04 11:20:31,910] INFO Receive messages:277500 (org.apache.tubemq.example.MsgRecvStats)
```
---
diff --git a/docs/zh-cn/tubemq_perf_test_vs_Kafka_cn.md b/docs/zh-cn/tubemq_perf_test_vs_Kafka_cn.md
index 27d131e..45916f6 100644
--- a/docs/zh-cn/tubemq_perf_test_vs_Kafka_cn.md
+++ b/docs/zh-cn/tubemq_perf_test_vs_Kafka_cn.md
@@ -1,8 +1,8 @@
-# inlong VS Kafka性能对比测试总结
+# TubeMQ VS Kafka性能对比测试总结
## 背景
-inlong是腾讯大数据自研的分布式消息中间件。其系统架构思想源于[Apache Kafka](http://kafka.apache.org/)。在实现上，则完全采取自适应的方式，结合实战做了很多优化及研发工作，如分区管理、分配机制和全新节点通讯流程，自主开发高性能的底层RPC通讯模块等。
-这些实现使得inlong在保证实时性和一致性的前提下，具有很好的健壮性及更高的吞吐能力。结合目前主流消息中间件使用情况，以Kafka为参照做性能对比测试，对比常规应用场景下两套系统性能。
+TubeMQ是腾讯大数据自研的分布式消息中间件。其系统架构思想源于[Apache Kafka](http://kafka.apache.org/)。在实现上，则完全采取自适应的方式，结合实战做了很多优化及研发工作，如分区管理、分配机制和全新节点通讯流程，自主开发高性能的底层RPC通讯模块等。
+这些实现使得TubeMQ在保证实时性和一致性的前提下，具有很好的健壮性及更高的吞吐能力。结合目前主流消息中间件使用情况，以Kafka为参照做性能对比测试，对比常规应用场景下两套系统性能。
## 测试场景方案
如下是我们根据实际应用场景设计的测试方案：
@@ -13,23 +13,23 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
角色|测试场景|要点
:---:|:---:|---
-闪电侠|场景五|快 (数据生产消费时延 inlong 10ms vs kafka 250ms )
-绿巨人|场景三，场景四|抗击打能力 (随着topic数由100,200,到500,1000逐步增大，inlong系统能力不减，吞吐量随负载的提升下降微小且能力持平 vs kafka吞吐量明显下降且不稳定；过滤消费时，inlong入出流量提升直接完胜kafka的入流量下降且吞吐量下降)
-蜘蛛侠|场景八|各个场景来去自如(不同机型下对比测试，inlong吞吐量稳定 vs Kafka在BX1机型下性能更低的问题)
-钢铁侠|场景二，场景三，场景六|自动化(系统运行中inlong可以动态实时的调整系统设置、消费行为来提升系统性能）
+闪电侠|场景五|快 (数据生产消费时延 TubeMQ 10ms vs kafka 250ms )
+绿巨人|场景三，场景四|抗击打能力 (随着topic数由100,200,到500,1000逐步增大，TubeMQ系统能力不减，吞吐量随负载的提升下降微小且能力持平 vs kafka吞吐量明显下降且不稳定；过滤消费时，TubeMQ入出流量提升直接完胜kafka的入流量下降且吞吐量下降)
+蜘蛛侠|场景八|各个场景来去自如(不同机型下对比测试，TubeMQ吞吐量稳定 vs Kafka在BX1机型下性能更低的问题)
+钢铁侠|场景二，场景三，场景六|自动化(系统运行中TubeMQ可以动态实时的调整系统设置、消费行为来提升系统性能）
具体的数据分析来看：
-1. 单Topic单实例配置下，inlong吞吐量要远低于Kafka；单Topic多实例配置下，inlong在4个实例时吞吐量追上Kafka对应5个分区配置，同时inlong的吞吐量随实例数增加而增加，Kafka出现不升反降的情况；inlong可以在系统运行中通过调整各项参数来动态的控制吞吐量的提升；
-2. 多Topic多实例配置下，inlong吞吐量维持在一个非常稳定的范围，且资源消耗，包括文件句柄、网络连接句柄数等非常的低；Kafka吞吐量随Topic数增多呈现明显的下降趋势，且资源消耗急剧增大；在SATA盘存储条件下，随着机型的配置提升，inlong吞吐量可以直接压到磁盘瓶颈，而Kafka呈现不稳定状态；在CG1机型SSD盘情况下，Kafka的吞吐量要好于inlong；
-3. 在过滤消费时，inlong可以极大地降低服务端的网络出流量，同时还会因过滤消费消耗的资源少于全量消费，反过来促进inlong吞吐量提升；kafka无服务端过滤，出流量与全量消费一致，流量无明显的节约；
-4. 资源消耗方面各有差异：inlong由于采用顺序写随机读，CPU消耗很大，Kafka采用顺序写块读，CPU消耗很小，但其他资源，如文件句柄、网络连接等消耗非常的大。在实际的SAAS模式下的运营环境里，Kafka会因为zookeeper依赖出现系统瓶颈，会因生产、消费、Broker众多，受限制的地方会更多，比如文件句柄、网络连接数等，资源消耗会更大；
+1. 单Topic单实例配置下，TubeMQ吞吐量要远低于Kafka；单Topic多实例配置下，TubeMQ在4个实例时吞吐量追上Kafka对应5个分区配置，同时TubeMQ的吞吐量随实例数增加而增加，Kafka出现不升反降的情况；TubeMQ可以在系统运行中通过调整各项参数来动态的控制吞吐量的提升；
+2. 多Topic多实例配置下，TubeMQ吞吐量维持在一个非常稳定的范围，且资源消耗，包括文件句柄、网络连接句柄数等非常的低；Kafka吞吐量随Topic数增多呈现明显的下降趋势，且资源消耗急剧增大；在SATA盘存储条件下，随着机型的配置提升，TubeMQ吞吐量可以直接压到磁盘瓶颈，而Kafka呈现不稳定状态；在CG1机型SSD盘情况下，Kafka的吞吐量要好于TubeMQ；
+3. 在过滤消费时，TubeMQ可以极大地降低服务端的网络出流量，同时还会因过滤消费消耗的资源少于全量消费，反过来促进TubeMQ吞吐量提升；kafka无服务端过滤，出流量与全量消费一致，流量无明显的节约；
+4. 资源消耗方面各有差异：TubeMQ由于采用顺序写随机读，CPU消耗很大，Kafka采用顺序写块读，CPU消耗很小，但其他资源，如文件句柄、网络连接等消耗非常的大。在实际的SAAS模式下的运营环境里，Kafka会因为zookeeper依赖出现系统瓶颈，会因生产、消费、Broker众多，受限制的地方会更多，比如文件句柄、网络连接数等，资源消耗会更大；
## 测试环境及配置
###【软件版本及部署环境】
-**角色**|**inlong**|**Kafka**
+**角色**|**TubeMQ**|**Kafka**
:---:|---|---
-**软件版本**|inlong-3.8.0|Kafka\_2.11-0.10.2.0
+**软件版本**|tubemq-3.8.0|Kafka\_2.11-0.10.2.0
**zookeeper部署**|与Broker不在同一台机器上，单机|与Broker配置不在同一台机器，单机
**Broker部署**|单机|单机
**Master部署**|与Broker不在同一台机器上，单机|不涉及
@@ -46,40 +46,40 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
###【Broker系统配置】
-| **配置项** | **inlong Broker** | **Kafka Broker** |
+| **配置项** | **TubeMQ Broker** | **Kafka Broker** |
|:---:|---|---|
| **日志存储** | Raid10处理后的SATA盘或SSD盘 | Raid10处理后的SATA盘或SSD盘 |
-| **启动参数** | BROKER_JVM_ARGS="-Dcom.sun.management.jmxremote -server -Xmx24g -Xmn8g -XX:SurvivorRatio=6 -XX:+UseMembar -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSScavengeBeforeRemark -XX:ParallelCMSThreads=4 -XX:+UseCMSCompactAtFullCollection -verbose:gc -Xloggc:$BASE_DIR/logs/gc.log.`date +%Y-%m-%d-%H-%M-%S` -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+CMSClassUnloadingEnabled -XX:CMSInitiatingOccupancyFraction=75 -XX:CMSFullGCsBeforeCompaction=1 -Dsun.net [...]
-| **配置文件** | 在inlong-3.8.0版本broker.ini配置文件上改动: consumerRegTimeoutMs=35000<br>tcpWriteServiceThread=50<br>tcpReadServiceThread=50<br>primaryPath为SATA盘日志目录|kafka_2.11-0.10.2.0版本server.properties配置文件上改动：<br>log.flush.interval.messages=5000<br>log.flush.interval.ms=10000<br>log.dirs为SATA盘日志目录<br>socket.send.buffer.bytes=1024000<br>socket.receive.buffer.bytes=1024000<br>socket.request.max.bytes=2147483600<br>log.segment.bytes=1073741824<br>num.network.threads=25<br>num.io.threads=48< [...]
+| **启动参数** | BROKER_JVM_ARGS="-Dcom.sun.management.jmxremote -server -Xmx24g -Xmn8g -XX:SurvivorRatio=6 -XX:+UseMembar -XX:+UseConcMarkSweepGC -XX:+CMSParallelRemarkEnabled -XX:+CMSScavengeBeforeRemark -XX:ParallelCMSThreads=4 -XX:+UseCMSCompactAtFullCollection -verbose:gc -Xloggc:$BASE_DIR/logs/gc.log.`date +%Y-%m-%d-%H-%M-%S` -XX:+PrintGCDetails -XX:+PrintGCDateStamps -XX:+CMSClassUnloadingEnabled -XX:CMSInitiatingOccupancyFraction=75 -XX:CMSFullGCsBeforeCompaction=1 -Dsun.net [...]
+| **配置文件** | 在tubemq-3.8.0版本broker.ini配置文件上改动: consumerRegTimeoutMs=35000<br>tcpWriteServiceThread=50<br>tcpReadServiceThread=50<br>primaryPath为SATA盘日志目录|kafka_2.11-0.10.2.0版本server.properties配置文件上改动：<br>log.flush.interval.messages=5000<br>log.flush.interval.ms=10000<br>log.dirs为SATA盘日志目录<br>socket.send.buffer.bytes=1024000<br>socket.receive.buffer.bytes=1024000<br>socket.request.max.bytes=2147483600<br>log.segment.bytes=1073741824<br>num.network.threads=25<br>num.io.threads=48< [...]
| **其它** | 除测试用例里特别指定，每个topic创建时设置：<br>memCacheMsgSizeInMB=5<br>memCacheFlushIntvl=20000<br>memCacheMsgCntInK=10 <br>unflushThreshold=5000<br>unflushInterval=10000<br>unFlushDataHold=5000 | 客户端代码里设置：<br>生产端：<br>props.put("key.serializer", "org.apache.kafka.common.serialization.StringSerializer");<br>props.put("value.serializer", "org.apache.kafka.common.serialization.StringSerializer");<br>props.put("linger.ms", "200");<br>props.put("block.on.buffer.full", false);<br>props.pu [...]
## 测试场景及结论
-### 场景一：基础场景，单topic情况，一入两出模型，分别使用不同的消费模式、不同大小的消息包，分区逐步做横向扩展，对比inlong和Kafka性能
+### 场景一：基础场景，单topic情况，一入两出模型，分别使用不同的消费模式、不同大小的消息包，分区逐步做横向扩展，对比TubeMQ和Kafka性能
####【结论】
在单topic不同分区的情况下：
-1. inlong吞吐量不随分区变化而变化，同时inlong属于顺序写随机读模式，单实例情况下吞吐量要低于Kafka，CPU要高于Kafka；
+1. TubeMQ吞吐量不随分区变化而变化，同时TubeMQ属于顺序写随机读模式，单实例情况下吞吐量要低于Kafka，CPU要高于Kafka；
2. Kafka随着分区增多吞吐量略有下降，CPU使用率很低；
-3. inlong分区由于是逻辑分区，增加分区不影响吞吐量；Kafka分区为物理文件的增加，但增加分区入出流量反而会下降；
+3. TubeMQ分区由于是逻辑分区，增加分区不影响吞吐量；Kafka分区为物理文件的增加，但增加分区入出流量反而会下降；
####【指标】
-### 场景二：单topic情况，一入两出模型，固定消费包大小，横向扩展实例数，对比inlong和Kafka性能情况
+### 场景二：单topic情况，一入两出模型，固定消费包大小，横向扩展实例数，对比TubeMQ和Kafka性能情况
####【结论】
从场景一和场景二的测试数据结合来看：
-1. inlong随着实例数增多，吞吐量增长，在4个实例的时候吞吐量与Kafka持平，磁盘IO使用率比Kafka低，CPU使用率比Kafka高；
-2. inlong的消费方式影响到系统的吞吐量，内存读取模式（301）性能低于文件读取模式（101），但能降低消息的时延；
+1. TubeMQ随着实例数增多，吞吐量增长，在4个实例的时候吞吐量与Kafka持平，磁盘IO使用率比Kafka低，CPU使用率比Kafka高；
+2. TubeMQ的消费方式影响到系统的吞吐量，内存读取模式（301）性能低于文件读取模式（101），但能降低消息的时延；
3. Kafka随分区实例数增多，没有如期提升系统吞吐量；
-4. inlong按照Kafka等同的增加实例（物理文件）后，吞吐量量随之提升，在4个实例的时候测试效果达到并超过Kafka
- 5个分区的状态；inlong可以根据业务或者系统配置需要，调整数据读取方式，可以动态提升系统的吞吐量；Kafka随着分区增加，入流量有下降；
+4. TubeMQ按照Kafka等同的增加实例（物理文件）后，吞吐量量随之提升，在4个实例的时候测试效果达到并超过Kafka
+ 5个分区的状态；TubeMQ可以根据业务或者系统配置需要，调整数据读取方式，可以动态提升系统的吞吐量；Kafka随着分区增加，入流量有下降；
####【指标】
@@ -89,19 +89,19 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
读取模式通过admin\_upd\_def\_flow\_control\_rule设置qryPriorityId为对应值.
-### 场景三：多topic场景，固定消息包大小、实例及分区数，考察100、200、500、1000个topic场景下inlong和Kafka性能情况
+### 场景三：多topic场景，固定消息包大小、实例及分区数，考察100、200、500、1000个topic场景下TubeMQ和Kafka性能情况
####【结论】
按照多Topic场景下测试：
-1. inlong随着Topic数增加，生产和消费性能维持在一个均线上，没有特别大的流量波动，占用的文件句柄、内存量、网络连接数不多（1k
+1. TubeMQ随着Topic数增加，生产和消费性能维持在一个均线上，没有特别大的流量波动，占用的文件句柄、内存量、网络连接数不多（1k
topic下文件句柄约7500个，网络连接150个），但CPU占用比较大；
-2. inlong通过调整消费方式由内存消费转为文件消费方式后，吞吐量有比较大的增长，CPU占用率有下降，对不同性能要求的业务可以进行区别服务；
+2. TubeMQ通过调整消费方式由内存消费转为文件消费方式后，吞吐量有比较大的增长，CPU占用率有下降，对不同性能要求的业务可以进行区别服务；
3. Kafka随着Topic数的增加，吞吐量有明显的下降，同时Kafka流量波动较为剧烈，长时间运行存消费滞后，以及吞吐量明显下降的趋势，以及内存、文件句柄、网络连接数量非常大(在1K
Topic配置时，网络连接达到了1.2W，文件句柄达到了4.5W)等问题；
-4. 数据对比来看，inlong相比Kafka运行更稳定，吞吐量以稳定形势呈现，长时间跑吞吐量不下降，资源占用少，但CPU的占用需要后续版本解决；
+4. 数据对比来看，TubeMQ相比Kafka运行更稳定，吞吐量以稳定形势呈现，长时间跑吞吐量不下降，资源占用少，但CPU的占用需要后续版本解决；
####【指标】
@@ -112,8 +112,8 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. inlong采用服务端过滤的模式，出流量指标与入流量存在明显差异；
-2. inlong服务端过滤提供了更多的资源给到生产，生产性能比非过滤情况有提升；
+1. TubeMQ采用服务端过滤的模式，出流量指标与入流量存在明显差异；
+2. TubeMQ服务端过滤提供了更多的资源给到生产，生产性能比非过滤情况有提升；
3. Kafka采用客户端过滤模式，入流量没有提升，出流量差不多是入流量的2倍，同时入出流量不稳定；
####【指标】
@@ -121,20 +121,20 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
**注：** 如下场景中，topic为100，包长均为1K，分区数均为10
-### 场景五：inlong、Kafka数据消费时延比对
+### 场景五：TubeMQ、Kafka数据消费时延比对
| 类型 | 时延 | Ping时延 |
|---|---|---|
-| inlong | 90%数据在10ms± | C->B：0.05ms ~ 0.13ms, P->B：2.40ms ~ 2.42ms |
+| TubeMQ | 90%数据在10ms± | C->B：0.05ms ~ 0.13ms, P->B：2.40ms ~ 2.42ms |
| Kafka | 90%集中在250ms± | C->B：0.05ms ~ 0.07ms, P-\>B：2.95ms \~ 2.96ms |
-备注：inlong的消费端存在一个等待队列处理消息追平生产时的数据未找到的情况，缺省有200ms的等待时延。测试该项时，inlong消费端要调整拉取时延（ConsumerConfig.setMsgNotFoundWaitPeriodMs()）为10ms，或者设置频控策略为10ms。
+备注：TubeMQ的消费端存在一个等待队列处理消息追平生产时的数据未找到的情况，缺省有200ms的等待时延。测试该项时，TubeMQ消费端要调整拉取时延（ConsumerConfig.setMsgNotFoundWaitPeriodMs()）为10ms，或者设置频控策略为10ms。
### 场景六：调整Topic配置的内存缓存大小（memCacheMsgSizeInMB）对吞吐量的影响
####【结论】
-1. inlong调整Topic的内存缓存大小能对吞吐量形成正面影响，实际使用时可以根据机器情况合理调整；
+1. TubeMQ调整Topic的内存缓存大小能对吞吐量形成正面影响，实际使用时可以根据机器情况合理调整；
2. 从实际使用情况看，内存大小设置并不是越大越好，需要合理设置该值；
####【指标】
@@ -147,9 +147,9 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. 消费严重滞后情况下，inlong和Kafka都会因磁盘IO飙升使得生产消费受阻；
-2. 在带SSD系统里，inlong可以通过SSD转存储消费来换取部分生产和消费入流量；
-3. 按照版本计划，目前inlong的SSD消费转存储特性不是最终实现，后续版本中将进一步改进，使其达到最合适的运行方式；
+1. 消费严重滞后情况下，TubeMQ和Kafka都会因磁盘IO飙升使得生产消费受阻；
+2. 在带SSD系统里，TubeMQ可以通过SSD转存储消费来换取部分生产和消费入流量；
+3. 按照版本计划，目前TubeMQ的SSD消费转存储特性不是最终实现，后续版本中将进一步改进，使其达到最合适的运行方式；
####【指标】
@@ -160,17 +160,17 @@ inlong是腾讯大数据自研的分布式消息中间件。其系统架构思
####【结论】
-1. inlong在BX1机型下较TS60机型有更高的吞吐量，同时因IO util达到瓶颈无法再提升，吞吐量在CG1机型下又较BX1达到更高的指标值；
+1. TubeMQ在BX1机型下较TS60机型有更高的吞吐量，同时因IO util达到瓶颈无法再提升，吞吐量在CG1机型下又较BX1达到更高的指标值；
2. Kafka在BX1机型下系统吞吐量不稳定，且较TS60下测试的要低，在CG1机型下系统吞吐量达到最高，万兆网卡跑满；
-3. 在SATA盘存储条件下，inlong性能指标随着硬件配置的改善有明显的提升；Kafka性能指标随硬件机型的改善存在不升反降的情况;
-4. 在SSD盘存储条件下，Kafka性能指标达到最好，inlong指标不及Kafka；
+3. 在SATA盘存储条件下，TubeMQ性能指标随着硬件配置的改善有明显的提升；Kafka性能指标随硬件机型的改善存在不升反降的情况;
+4. 在SSD盘存储条件下，Kafka性能指标达到最好，TubeMQ指标不及Kafka；
5. CG1机型数据存储盘较小(仅2.2T)，RAID 10配置下90分钟以内磁盘即被写满，无法测试两系统长时间运行情况。
####【指标】
**注1:** 如下场景Topic数均配置500个topic，10个分区，消息包大小为1K字节;
-**注2:** inlong采用的是301内存读取模式消费；
+**注2:** TubeMQ采用的是301内存读取模式消费；
## 附录1 不同机型下资源占用情况图：
diff --git a/en-us/community/index.html b/en-us/community/index.html
index 5a8d666..afa9ce9 100644
--- a/en-us/community/index.html
+++ b/en-us/community/index.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="keyword1,keyword2" />
<meta name="description" content="page description" />
<!-- 网页标签标题 -->
- <title>Apache inlong</title>
+ <title>Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/community.css" />
</head>
diff --git a/en-us/docs/architecture.html b/en-us/docs/architecture.html
index 0727c9e..984041a 100644
--- a/en-us/docs/architecture.html
+++ b/en-us/docs/architecture.html
@@ -7,20 +7,20 @@
<meta name="keywords" content="architecture" />
<meta name="description" content="architecture" />
<!-- 网页标签标题 -->
- <title>Architecture - Apache inlong</title>
+ <title>Architecture - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>After years of evolution, the inlong cluster is divided into the following 5 parts:
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>After years of evolution, the TubeMQ cluster is divided into the following 5 parts:
<img src="img/sys_structure.png" alt=""></p>
<ul>
<li>
<p><strong>Portal：</strong> The Portal part responsible for external interaction and maintenance operations, including API and Web. The API connects to the management system outside the cluster. The Web is a page encapsulation of daily operation and maintenance functions based on the API;</p>
</li>
<li>
-<p><strong>Master：</strong> It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using inlong Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, meta [...]
+<p><strong>Master：</strong> It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using TubeMQ Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, meta [...]
</li>
<li>
<p><strong>Broker：</strong> The Store part responsible for data storage. This part is composed of independent Broker nodes. Each Broker node manages the Topic set in this node, including the addition, deletion, modification, and inquiring about Topics. It is also responsible for message storage, consumption, aging, partition expansion, data consumption offset records, etc. on the topic, and the external capabilities of the cluster, including the number of topics, throughput, and capacity [...]
@@ -33,10 +33,10 @@
</li>
</ul>
<h2>Broker File Storage Scheme Improvement：</h2>
-<p>Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,inlong is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, inlong has made some improvements:</p>
+<p>Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,TubeMQ is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, TubeMQ has made some improvements:</p>
<ol>
<li>
-<p><strong>File structure and organization adjustment:</strong> inlong's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
+<p><strong>File structure and organization adjustment:</strong> TubeMQ's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
<img src="img/store_file.png" alt=""></p>
</li>
<li>
diff --git a/en-us/docs/architecture.json b/en-us/docs/architecture.json
index 72e9516..e1ad347 100644
--- a/en-us/docs/architecture.json
+++ b/en-us/docs/architecture.json
@@ -1,8 +1,8 @@
{
"filename": "architecture.md",
- "__html": "<h2>inlong Architecture：</h2>\n<p>After years of evolution, the inlong cluster is divided into the following 5 parts: \n<img src=\"img/sys_structure.png\" alt=\"\"></p>\n<ul>\n<li>\n<p><strong>Portal：</strong> The Portal part responsible for external interaction and maintenance operations, including API and Web. The API connects to the management system outside the cluster. The Web is a page encapsulation of daily operation and maintenance functions based on the API;</p>\n</ [...]
+ "__html": "<h2>TubeMQ Architecture：</h2>\n<p>After years of evolution, the TubeMQ cluster is divided into the following 5 parts: \n<img src=\"img/sys_structure.png\" alt=\"\"></p>\n<ul>\n<li>\n<p><strong>Portal：</strong> The Portal part responsible for external interaction and maintenance operations, including API and Web. The API connects to the management system outside the cluster. The Web is a page encapsulation of daily operation and maintenance functions based on the API;</p>\n</ [...]
"link": "/en-us/docs/architecture.html",
"meta": {
- "title": "Architecture - Apache inlong"
+ "title": "Architecture - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/architecture.md b/en-us/docs/architecture.md
index 43e48db..a0ee089 100644
--- a/en-us/docs/architecture.md
+++ b/en-us/docs/architecture.md
@@ -1,14 +1,14 @@
---
-title: Architecture - Apache inlong
+title: Architecture - Apache TubeMQ
---
-## inlong Architecture： ##
-After years of evolution, the inlong cluster is divided into the following 5 parts:
+## TubeMQ Architecture： ##
+After years of evolution, the TubeMQ cluster is divided into the following 5 parts:
- **Portal：** The Portal part responsible for external interaction and maintenance operations, including API and Web. The API connects to the management system outside the cluster. The Web is a page encapsulation of daily operation and maintenance functions based on the API;
-- **Master：** It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using inlong Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, metadata query, etc;
+- **Master：** It is responsible for the Control part of the cluster. This part is composed of one or more Master nodes. Master HA performs heartbeat keep-alive and real-time hot standby switching between master nodes (This is the reason why everyone needs to fill in the addresses of all Master nodes corresponding to the cluster when using TubeMQ Lib). The main master is responsible for managing the status of the entire cluster, resource scheduling, permission checking, metadata query, etc;
- **Broker：** The Store part responsible for data storage. This part is composed of independent Broker nodes. Each Broker node manages the Topic set in this node, including the addition, deletion, modification, and inquiring about Topics. It is also responsible for message storage, consumption, aging, partition expansion, data consumption offset records, etc. on the topic, and the external capabilities of the cluster, including the number of topics, throughput, and capacity, are complete [...]
@@ -17,9 +17,9 @@ After years of evolution, the inlong cluster is divided into the following 5 par
- **Zookeeper：** Responsible for the zk part of the offset storage. This part of the function has been weakened to only the persistent storage of the offset. Considering the next multi-node copy function, this module is temporarily reserved;
## Broker File Storage Scheme Improvement： ##
-Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,inlong is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, inlong has made some improvements:
+Systems that use disk as a medium for data persistence are faced with a variety of performance issues caused by disk problems,TubeMQ is no exception. Performance improvements are largely addressed to solve the problem of how message data is read, write and stored. In this respect, TubeMQ has made some improvements:
-1. **File structure and organization adjustment:** inlong's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
+1. **File structure and organization adjustment:** TubeMQ's disk storage scheme is similar to Kafka, but not the same, as the figure shown below. Storage instance is consisted of an index file and a data file, each topic can allocate one or more storage instances. And each topic separately maintains the mechanisms of managing storage instances, including aging cycles, number of partitions, whether readable or writable, etc.
2. **Memory block cache:** We add an additional memory cache block for each storage instance based on the file storage, i.e. add a piece of memory to the original write disk to isolate the slow impact of hard disk. The data is brushed into memory first, and the memory control block then brushes the data to disk files in bulk.
diff --git a/en-us/docs/client_rpc.html b/en-us/docs/client_rpc.html
index e5d9747..fc92963 100644
--- a/en-us/docs/client_rpc.html
+++ b/en-us/docs/client_rpc.html
@@ -7,24 +7,24 @@
<meta name="keywords" content="client_rpc" />
<meta name="description" content="client_rpc" />
<!-- 网页标签标题 -->
- <title>Client RPC - Apache inlong</title>
+ <title>Client RPC - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<h2>General Introduction</h2>
-<p>Implements of this part can be found in <code>org.apache.inlong.corerpc</code>. Each node in Apache inlong Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
+<p>Implements of this part can be found in <code>org.apache.tubemq.corerpc</code>. Each node in Apache TubeMQ Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
<img src="img/client_rpc/rpc_bytes_def.png" alt=""></p>
-<p>All we can see in TCP are binary streams. We defind a 4-byte msgToken message <code>RPC\_PROTOCOL\_BEGIN\_TOKEN</code> in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by inlong or something wrong may happended. Follows is a 4-byte serialNo, this fi [...]
-<p>We defined <code>listSize</code> as <code>\&lt;len\&gt;\&lt;data\&gt;</code> because serialized PB data is saved as a ByteBuffer object in inlong, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.</p>
+<p>All we can see in TCP are binary streams. We defind a 4-byte msgToken message <code>RPC\_PROTOCOL\_BEGIN\_TOKEN</code> in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by TubeMQ or something wrong may happended. Follows is a 4-byte serialNo, this fi [...]
+<p>We defined <code>listSize</code> as <code>\&lt;len\&gt;\&lt;data\&gt;</code> because serialized PB data is saved as a ByteBuffer object in TubeMQ, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.</p>
<p><strong>Pay more attention when implementing multiple languages and SDKs.</strong> Need to serialize PB data content into arrays of blocks(supported in PB codecs).</p>
<h2>PB format code:</h2>
<p>PB format encoding is divided into RPC framework definition, to the Master message encoding and to the Broker message encoding of three parts, you can use protobuf directly compiled to get different language codecs, it is very convenient to use.
<img src="img/client_rpc/rpc_proto_def.png" alt=""></p>
<p><code>RPC.proto</code> defines 6 struct, which divided into 2 class: Request message and Response message. Response message is divided into Successful Response and Exception Response.
<img src="img/client_rpc/rpc_pbmsg_structure.png" alt=""></p>
-<p>The request message encoding and response message decoding can be implemented in the <code>NettyClient.java</code> class. There is some room for improvement in this part of the definition and can be found in <a href="https://issues.apache.org/jira/browse/inlong-109">inlong-109</a>. However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol impl [...]
+<p>The request message encoding and response message decoding can be implemented in the <code>NettyClient.java</code> class. There is some room for improvement in this part of the definition and can be found in <a href="https://issues.apache.org/jira/browse/TUBEMQ-109">TUBEMQ-109</a>. However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol impl [...]
<img src="img/client_rpc/rpc_conn_detail.png" alt=""></p>
<p>Flag marks whether the message is requested or not, and the next three marks represent the content of the message trace, which is not currently used; the related is a fixed mapping of the service type, protocol version, service type, etc., the more critical parameter RequestBody.timeout is the maximum allowable time from when a request is received by the server to when it is actually processed. Long wait time, discarded if exceeded, current default is 10 seconds, request filled as follows.
<img src="img/client_rpc/rpc_header_fill.png" alt=""></p>
@@ -51,7 +51,7 @@
<p><strong>Consumer Interaction Diagram</strong>:</p>
<p>Consumer has 7 pairs of command in all, Register, Heartbeat, Exit to Master; Register, Logout, Heartbeat, Pulling mseeage to Broker. Registration and Logout to Broker is the same command, indicated by a different status code.</p>
<p><img src="img/client_rpc/rpc_consumer_diagram.png" alt=""></p>
-<p>As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because inlong is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer [...]
+<p>As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because TubeMQ is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer [...]
<p>##Client feature:</p>
<table>
<thead>
@@ -323,7 +323,7 @@
<p><strong>msgType</strong> is the type of filter message. <code>msgTime</code> is the message time when the SDK sends a message, its value comes from the value filled in by <code>putSystemHeader</code> when constructing Message, and there is a corresponding API in Message to get it.</p>
<p><strong>requireAuth</strong>: Required authentication operations to Broker for data production, not currently in effect due to performance issues. The authAuthorizedToken value in the sent message is based on the value provided by the Master and will change with the change of the Master.</p>
<h2><strong>Partition Loadbalance</strong>:</h2>
-<p>Apache inlong currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.</p>
+<p>Apache TubeMQ currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.</p>
<p><strong>Server side load balancing</strong>:</p>
<ul>
<li>When the Master process starts, it starts the load-balancing thread balancerChore. balancerChore periodically checks the current registered consumer group for load balancing. The process is simply to evenly distribute the consumer group subscription partitions to registered clients, and periodically detect the current partition of the client If so, the extra partitions will be split to other clients with less number of subscriptions. First, the master checks if the current consumer g [...]
diff --git a/en-us/docs/client_rpc.json b/en-us/docs/client_rpc.json
index 35458bf..0667324 100644
--- a/en-us/docs/client_rpc.json
+++ b/en-us/docs/client_rpc.json
@@ -1,8 +1,8 @@
{
"filename": "client_rpc.md",
- "__html": "<h1>Definition of Apache inlong RPC</h1>\n<h2>General Introduction</h2>\n<p>Implements of this part can be found in <code>org.apache.inlong.corerpc</code>. Each node in Apache inlong Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.\n<img src=\"img/client_rpc/rpc_bytes_def.png\" alt=\"\"></p>\n<p>All we can see in TCP are binary streams. We defind a 4-byte msgToken message <code>RPC\\_PROTOCOL\\_BEGIN\\_TOKEN</code> in header, [...]
+ "__html": "<h1>Definition of Apache TubeMQ RPC</h1>\n<h2>General Introduction</h2>\n<p>Implements of this part can be found in <code>org.apache.tubemq.corerpc</code>. Each node in Apache TubeMQ Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.\n<img src=\"img/client_rpc/rpc_bytes_def.png\" alt=\"\"></p>\n<p>All we can see in TCP are binary streams. We defind a 4-byte msgToken message <code>RPC\\_PROTOCOL\\_BEGIN\\_TOKEN</code> in header, [...]
"link": "/en-us/docs/client_rpc.html",
"meta": {
- "title": "Client RPC - Apache inlong"
+ "title": "Client RPC - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/client_rpc.md b/en-us/docs/client_rpc.md
index 43b4037..e935b4e 100644
--- a/en-us/docs/client_rpc.md
+++ b/en-us/docs/client_rpc.md
@@ -1,17 +1,17 @@
---
-title: Client RPC - Apache inlong
+title: Client RPC - Apache TubeMQ
---
-# Definition of Apache inlong RPC
+# Definition of Apache TubeMQ RPC
## General Introduction
-Implements of this part can be found in `org.apache.inlong.corerpc`. Each node in Apache inlong Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
+Implements of this part can be found in `org.apache.tubemq.corerpc`. Each node in Apache TubeMQ Cluster Communicates by TCP Keep-Alive. Mseeages are definded using binary and protobuf combined.
-All we can see in TCP are binary streams. We defind a 4-byte msgToken message `RPC\_PROTOCOL\_BEGIN\_TOKEN` in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by inlong or something wrong may happended. Follows is a 4-byte serialNo, this field is sent by [...]
+All we can see in TCP are binary streams. We defind a 4-byte msgToken message `RPC\_PROTOCOL\_BEGIN\_TOKEN` in header, which are used to distinguish each message and identify the legitimacy of the counterpart. When message client received is not started with these header field, client needs to close the connection and prompt the error and quit or reconnect because the protocal is not supported by TubeMQ or something wrong may happended. Follows is a 4-byte serialNo, this field is sent by [...]
-We defined `listSize` as `\<len\>\<data\>` because serialized PB data is saved as a ByteBuffer object in inlong, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.
+We defined `listSize` as `\<len\>\<data\>` because serialized PB data is saved as a ByteBuffer object in TubeMQ, and in Java, there a maximum(8196) length of ByteBuffer block, an overlength PB message needs to be saved in several ByteBuffer. No total length was counted, and the ByteBuffer is directly written when Serializing in to TCP message.
**Pay more attention when implementing multiple languages and SDKs.** Need to serialize PB data content into arrays of blocks(supported in PB codecs).
@@ -24,7 +24,7 @@ PB format encoding is divided into RPC framework definition, to the Master messa
`RPC.proto` defines 6 struct, which divided into 2 class: Request message and Response message. Response message is divided into Successful Response and Exception Response.
-The request message encoding and response message decoding can be implemented in the `NettyClient.java` class. There is some room for improvement in this part of the definition and can be found in [inlong-109](https://issues.apache.org/jira/browse/inlong-109). However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol implementation module require [...]
+The request message encoding and response message decoding can be implemented in the `NettyClient.java` class. There is some room for improvement in this part of the definition and can be found in [TUBEMQ-109](https://issues.apache.org/jira/browse/TUBEMQ-109). However, due to compatibility concerns, it will be gradually replaced. We have implemented the current protobuf version, which is not a problem until at least 1.0.0. With the new protocol, the protocol implementation module require [...]
Flag marks whether the message is requested or not, and the next three marks represent the content of the message trace, which is not currently used; the related is a fixed mapping of the service type, protocol version, service type, etc., the more critical parameter RequestBody.timeout is the maximum allowable time from when a request is received by the server to when it is actually processed. Long wait time, discarded if exceeded, current default is 10 seconds, request filled as follows.
@@ -56,7 +56,7 @@ Consumer has 7 pairs of command in all, Register, Heartbeat, Exit to Master; Reg
-As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because inlong is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer in [...]
+As we can see from the above picture, the Consumer first has to register to the Master, but registering to the Master can not get Metadata information immediately because TubeMQ is using a server-side load-balancing model, and the client needs to wait for the server to dispatch the consumption partition information; Consumer to Broker needs to register the logout operation. Partition is exclusive at the time of consumption, i.e., the same partition can only be consumed by one consumer in [...]
##Client feature:
@@ -167,7 +167,7 @@ This part is related to the definition of RPC Message.
**Partition Loadbalance**:
----------
-Apache inlong currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.
+Apache TubeMQ currently uses a server-side load balancing mode, where the balancing process is managed and maintained by the server; subsequent versions will add a client-side load balancing mode, so that two modes can co-exist.
**Server side load balancing**:
diff --git a/en-us/docs/clients_java.html b/en-us/docs/clients_java.html
index c59d747..f45d525 100644
--- a/en-us/docs/clients_java.html
+++ b/en-us/docs/clients_java.html
@@ -7,28 +7,28 @@
<meta name="keywords" content="clients_java" />
<meta name="description" content="clients_java" />
<!-- 网页标签标题 -->
- <title>JAVA SDK API - Apache inlong</title>
+ <title>JAVA SDK API - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<hr>
<h3><strong>1. 基础对象接口介绍：</strong></h3>
<h4><strong>a) MessageSessionFactory（消息会话工厂）：</strong></h4>
-<p>inlong 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。</p>
+<p>TubeMQ 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。</p>
<h4><strong>b) MasterInfo:</strong></h4>
-<p>inlong的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于inlong Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于inlong的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。</p>
+<p>TubeMQ的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于TubeMQ Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于TubeMQ的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。</p>
<h4><strong>c) TubeClientConfig：</strong></h4>
-<p>MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与inlong-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前inlong的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。</p>
+<p>MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与TubeMQ-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前TubeMQ的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。</p>
<h4><strong>d) ConsumerConfig：</strong></h4>
<p>ConsumerConfig类是TubeClientConfig类的子类，它是在TubeClientConfig类基础上增加了Consumer类对象初始化时候的参数携带，因而在一个既有Producer又有Consumer的MessageSessionFactory（消息会话工厂）类对象里，会话工厂类的相关设置以MessageSessionFactory类初始化的内容为准，Consumer类对象按照创建时传递的初始化类对象为准。在consumer里又根据消费行为的不同分为Pull消费者和Push消费者两种，两种特有的参数通过参数接口携带“pull”或“push”不同特征进行区分。</p>
<h4><strong>e) Message：</strong></h4>
-<p>Message类是inlong里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与inlong系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增inlong系统填写的内容，并在后续的版本中，新增的inlong系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做inlong进行数据收发统计时消息时间统计维度用。</p>
+<p>Message类是TubeMQ里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与TubeMQ系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增TubeMQ系统填写的内容，并在后续的版本中，新增的TubeMQ系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做TubeMQ进行数据收发统计时消息时间统计维度用。</p>
<h4><strong>f) MessageProducer：</strong></h4>
<p>消息生产者类，该类完成消息的生产，消息发送分为同步发送和异步发送两种接口，目前消息采用Round Robin方式发往后端服务器，后续这块将考虑按照业务指定的算法进行后端服务器选择方式进行生产。该类使用时需要注意的是，我们支持在初始化时候全量Topic指定的publish，也支持在生产过程中临时增加对新的Topic的publish，但临时增加的Topic不会立即生效，因而在使用新增Topic前，要先调用isTopicCurAcceptPublish接口查询该Topic是否已publish并且被服务器接受，否则有可能消息发送失败。</p>
<h4><strong>g) MessageConsumer：</strong></h4>
-<p>该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上inlong是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：</p>
+<p>该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上TubeMQ是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：</p>
<ul>
<li>
<p>a. CompleteSubscribe接口，带参数的接口支持客户端对指定的分区进行指定offset消费，不带参数的接口则按照ConsumerConfig.setConsumeModel(int consumeModel)接口进行对应的消费模式设置来消费数据;</p>
@@ -40,9 +40,9 @@
<hr>
<h3><strong>2. 接口调用示例：</strong></h3>
<h4><strong>a) 环境准备：</strong></h4>
-<p>inlong开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的inlong集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。</p>
+<p>TubeMQ开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的TubeMQ集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。</p>
<h4><strong>b) 创建Consumer：</strong></h4>
-<p>见包org.apache.inlong.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：</p>
+<p>见包org.apache.tubemq.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：</p>
<ul>
<li>
<h6><strong>i.初始化MessageConsumerExample类：</strong></h6>
@@ -140,7 +140,7 @@
}
</code></pre>
<h4><strong>c) 创建Producer：</strong></h4>
-<p>现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用inlong进行使用的场景，这里提供对应的使用demo，见包org.apache.inlong.example.MessageProducerExample类文件供参考，<strong>需要注意</strong>的是，业务除非使用数据平台的inlong集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：</p>
+<p>现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用TubeMQ进行使用的场景，这里提供对应的使用demo，见包org.apache.tubemq.example.MessageProducerExample类文件供参考，<strong>需要注意</strong>的是，业务除非使用数据平台的TubeMQ集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：</p>
<ul>
<li><strong>i. 初始化MessageProducerExample类：</strong></li>
</ul>
@@ -179,7 +179,7 @@
<ul>
<li><strong>iii. 进行数据生产：</strong></li>
</ul>
-<p>如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《inlong错误信息介绍.xlsx》：</p>
+<p>如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《TubeMQ错误信息介绍.xlsx》：</p>
<pre><code class="language-java"><span class="hljs-function"><span class="hljs-keyword">public</span> <span class="hljs-keyword">void</span> <span class="hljs-title">sendMessageAsync</span><span class="hljs-params">(<span class="hljs-keyword">int</span> id, <span class="hljs-keyword">long</span> currtime,
String topic, <span class="hljs-keyword">byte</span>[] body,
MessageSentCallback callback)</span> </span>{
@@ -205,7 +205,7 @@
<ul>
<li><strong>iv. Producer不同类MAMessageProducerExample关注点：</strong></li>
</ul>
-<p>该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（inlong通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。</p>
+<p>该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（TubeMQ通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。</p>
<p>自此，整个生产和消费的示例已经介绍完，大家可以直接下载对应的代码编译跑一边，看看是不是就是这么简单😊</p>
<hr>
<p><a href="#top">Back to top</a></p>
diff --git a/en-us/docs/clients_java.json b/en-us/docs/clients_java.json
index 420cbc8..266bb50 100644
--- a/en-us/docs/clients_java.json
+++ b/en-us/docs/clients_java.json
@@ -1,8 +1,8 @@
{
"filename": "clients_java.md",
- "__html": "<h2><strong>inlong Lib</strong> <strong>接口使用</strong></h2>\n<hr>\n<h3><strong>1. 基础对象接口介绍：</strong></h3>\n<h4><strong>a) MessageSessionFactory（消息会话工厂）：</strong></h4>\n<p>inlong 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以 [...]
+ "__html": "<h2><strong>TubeMQ Lib</strong> <strong>接口使用</strong></h2>\n<hr>\n<h3><strong>1. 基础对象接口介绍：</strong></h3>\n<h4><strong>a) MessageSessionFactory（消息会话工厂）：</strong></h4>\n<p>TubeMQ 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以 [...]
"link": "/en-us/docs/clients_java.html",
"meta": {
- "title": "JAVA SDK API - Apache inlong"
+ "title": "JAVA SDK API - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/clients_java.md b/en-us/docs/clients_java.md
index 5a6a3da..d2c5a8d 100644
--- a/en-us/docs/clients_java.md
+++ b/en-us/docs/clients_java.md
@@ -1,8 +1,8 @@
---
-title: JAVA SDK API - Apache inlong
+title: JAVA SDK API - Apache TubeMQ
---
-## **inlong Lib** **接口使用**
+## **TubeMQ Lib** **接口使用**
------
@@ -12,19 +12,19 @@ title: JAVA SDK API - Apache inlong
#### **a) MessageSessionFactory（消息会话工厂）：**
-inlong 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
+TubeMQ 采用MessageSessionFactory（消息会话工厂）来管理网络连接，又根据业务不同客户端是否复用连接细分为TubeSingleSessionFactory（单连接会话工厂）类和TubeMultiSessionFactory（多连接会话工厂）类2个部分，其实现逻辑大家可以从代码可以看到，单连接会话通过定义clientFactory静态类，实现了进程内不同客户端连接相同目标服务器时底层物理连接只建立一条的特征，多连接会话里定义的clientFactory为非静态类，从而实现同进程内通过不同会话工厂，创建的客户端所属的连接会话不同建立不同的物理连接。通过这种构造解决连接创建过多的问题，业务可以根据自身需要可以选择不同的消息会话工厂类，一般情况下我们使用单连接会话工厂类。
#### **b) MasterInfo:**
-inlong的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于inlong Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于inlong的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
+TubeMQ的Master地址信息对象，该对象的特点是支持配置多个Master地址，由于TubeMQ Master借助BDB的存储能力进行元数据管理，以及服务HA热切能力，Master的地址相应地就需要配置多条信息。该配置信息支持IP、域名两种模式，由于TubeMQ的HA是热切模式，客户端要保证到各个Master地址都是连通的。该信息在初始化TubeClientConfig类对象和ConsumerConfig类对象时使用，考虑到配置的方便性，我们将多条Master地址构造成“ip1:port1,ip2:port2,ip3:port3”格式并进行解析。
#### **c) TubeClientConfig：**
-MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与inlong-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前inlong的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
+MessageSessionFactory（消息会话工厂）初始化类，用来携带创建网络连接信息、客户端控制参数信息的对象类，包括RPC时长设置、Socket属性设置、连接质量检测参数设置、TLS参数设置、认证授权信息设置等信息，该类，连同接下来介绍的ConsumerConfig类，与TubeMQ-3.8.0版本之前版本的类变更最大的类，主要原因是在此之前TubeMQ的接口定义超6年多没有变更，接口使用上存在接口语义定义有歧义、接口属性设置单位不清晰、程序无法识别多种情况的内容选择等问题，考虑到代码开源自查问题方便性，以及新手学习成本问题，我们这次作了接口的重定义。对于重定义的前后差别，见配置接口定义说明部分介绍。
@@ -36,7 +36,7 @@ ConsumerConfig类是TubeClientConfig类的子类，它是在TubeClientConfig类
#### **e) Message：**
-Message类是inlong里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与inlong系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增inlong系统填写的内容，并在后续的版本中，新增的inlong系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做inlong进行数据收发统计时消息时间统计维度用。
+Message类是TubeMQ里传递的消息对象类，业务设置的data会从生产端原样传递给消息接收端，attribute内容是与TubeMQ系统共用的字段，业务填写的内容不会丢失和改写，但该字段有可能会新增TubeMQ系统填写的内容，并在后续的版本中，新增的TubeMQ系统内容有可能去掉而不被通知。该部分需要注意的是Message.putSystemHeader(final String msgType, final String msgTime)接口，该接口用来设置消息的消息类型和消息发送时间，msgType用于消费端过滤用，msgTime用做TubeMQ进行数据收发统计时消息时间统计维度用。
@@ -48,7 +48,7 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **g) MessageConsumer：**
-该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上inlong是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
+该类有两个子类PullMessageConsumer、PushMessageConsumer，通过这两个子类的包装，完成了对业务侧的Pull和Push语义。实际上TubeMQ是采用Pull模式与后端服务进行交互，为了便于业务的接口使用，我们进行了封装，大家可以看到其差别在于Push在启动时初始化了一个线程组，来完成主动的数据拉取操作。需要注意的地方在于：
- a. CompleteSubscribe接口，带参数的接口支持客户端对指定的分区进行指定offset消费，不带参数的接口则按照ConsumerConfig.setConsumeModel(int consumeModel)接口进行对应的消费模式设置来消费数据;
@@ -64,13 +64,13 @@ Message类是inlong里传递的消息对象类，业务设置的data会从生产
#### **a) 环境准备：**
-inlong开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的inlong集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
+TubeMQ开源包org.apache.tube.example里提供了生产和消费的具体代码示例，这里我们通过一个实际的例子来介绍如何填参和调用对应接口。首先我们搭建一个带3个Master节点的TubeMQ集群，3个Master地址及端口分别为test_1.domain.com，test_2.domain.com，test_3.domain.com，端口均为8080，在该集群里我们建立了若干个Broker，并且针对Broker我们创建了3个topic：topic_1，topic_2，topic_3等Topic配置；然后我们启动对应的Broker等待Consumer和Producer的创建。
#### **b) 创建Consumer：**
-见包org.apache.inlong.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
+见包org.apache.tubemq.example.MessageConsumerExample类文件，Consumer是一个包含网络交互协调的客户端对象，需要做初始化并且长期驻留内存重复使用的模型，它不适合单次拉起消费的场景。如下图示，我们定义了MessageConsumerExample封装类，在该类中定义了进行网络交互的会话工厂MessageSessionFactory类，以及用来做Push消费的PushMessageConsumer类：
- ###### **i.初始化MessageConsumerExample类：**
@@ -172,7 +172,7 @@ public class DefaultMessageListener implements MessageV2Listener {
#### **c) 创建Producer：**
-现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用inlong进行使用的场景，这里提供对应的使用demo，见包org.apache.inlong.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的inlong集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
+现网环境中业务的数据都是通过代理层来做接收汇聚，包装了比较多的异常处理，大部分的业务都没有也不会接触到TubeSDK的Producer类，考虑到业务自己搭建集群使用TubeMQ进行使用的场景，这里提供对应的使用demo，见包org.apache.tubemq.example.MessageProducerExample类文件供参考，**需要注意**的是，业务除非使用数据平台的TubeMQ集群做MQ服务，否则仍要按照现网的接入流程使用代理层来进行数据生产：
- **i. 初始化MessageProducerExample类：**
@@ -218,7 +218,7 @@ public void publishTopics(List<String> topicList) throws TubeClientException {
- **iii. 进行数据生产：**
-如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《inlong错误信息介绍.xlsx》：
+如下所示，则为具体的数据构造和发送逻辑，构造一个Message对象后调用sendMessage()函数发送即可，有同步接口和异步接口选择，依照业务要求选择不同接口；需要注意的是该业务根据不同消息调用message.putSystemHeader()函数设置消息的过滤属性和发送时间，便于系统进行消息过滤消费，以及指标统计用。完成这些，一条消息即被发送出去，如果返回结果为成功，则消息被成功的接纳并且进行消息处理，如果返回失败，则业务根据具体错误码及错误提示进行判断处理，相关错误详情见《TubeMQ错误信息介绍.xlsx》：
```java
public void sendMessageAsync(int id, long currtime,
@@ -248,7 +248,7 @@ public void sendMessageAsync(int id, long currtime,
- **iv. Producer不同类MAMessageProducerExample关注点：**
-该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（inlong通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
+该类初始化与MessageProducerExample类不同，采用的是TubeMultiSessionFactory多会话工厂类进行的连接初始化，该demo提供了如何使用多会话工厂类的特性，可以用于通过多个物理连接提升系统吞吐量的场景（TubeMQ通过连接复用模式来减少物理连接资源的使用），恰当使用可以提升系统的生产性能。在Consumer侧也可以通过多会话工厂进行初始化，但考虑到消费是长时间过程处理，对连接资源的占用比较小，消费场景不推荐使用。
diff --git a/en-us/docs/configure_introduction.html b/en-us/docs/configure_introduction.html
index f1c7690..3b08515 100644
--- a/en-us/docs/configure_introduction.html
+++ b/en-us/docs/configure_introduction.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="configure_introduction" />
<meta name="description" content="configure_introduction" />
<!-- 网页标签标题 -->
- <title>Configure Introduction - Apache inlong</title>
+ <title>Configure Introduction - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>The inlong server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, inlong. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separat [...]
-<p>Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the inlong-server-3.8.0/conf/ directory.</p>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>The TubeMQ server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, TubeMQ. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separat [...]
+<p>Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the tubemq-server-3.8.0/conf/ directory.</p>
<p>Their configuration is defined by a set of configuration units. The Master configuration consists of four mandatory units: [master], [zookeeper], [bdbStore], and optional [tlsSetting]. The Broker configuration is mandatory. Broker], [zookeeper] and optional [tlsSetting] consist of a total of 3 configuration units; in actual use, you can also combine the contents of the two configuration files into one ini file.</p>
<p>In addition to the back-end system configuration file, the Master also stores the Web front-end page module in the resources. The root directory velocity.properties file of the resources is the Web front-end page configuration file of the Master.</p>
<h2>Configuration item details:</h2>
@@ -181,7 +181,7 @@
<td>metaDataPath</td>
<td>no</td>
<td>string</td>
-<td>Metadata storage path. Absolute, or relative to inlong base directory (<code>$BASE_DIR</code>). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior <code>0.5.0</code>.</td>
+<td>Metadata storage path. Absolute, or relative to TubeMQ base directory (<code>$BASE_DIR</code>). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior <code>0.5.0</code>.</td>
</tr>
</tbody>
</table>
@@ -255,7 +255,7 @@
<td>repGroupName</td>
<td>no</td>
<td>string</td>
-<td>Cluster name, the primary and backup master node values must be the same. Optional field, default is "inlongMasterGroup".</td>
+<td>Cluster name, the primary and backup master node values must be the same. Optional field, default is "tubemqMasterGroup".</td>
</tr>
<tr>
<td>repNodeName</td>
diff --git a/en-us/docs/configure_introduction.json b/en-us/docs/configure_introduction.json
index 166ab74..b150d2c 100644
--- a/en-us/docs/configure_introduction.json
+++ b/en-us/docs/configure_introduction.json
@@ -1,8 +1,8 @@
{
"filename": "configure_introduction.md",
- "__html": "<h1>inlong configuration item description</h1>\n<p>The inlong server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, inlong. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib pa [...]
+ "__html": "<h1>TubeMQ configuration item description</h1>\n<p>The TubeMQ server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, TubeMQ. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib pa [...]
"link": "/en-us/docs/configure_introduction.html",
"meta": {
- "title": "Configure Introduction - Apache inlong"
+ "title": "Configure Introduction - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/configure_introduction.md b/en-us/docs/configure_introduction.md
index 82d0691..3ae8962 100644
--- a/en-us/docs/configure_introduction.md
+++ b/en-us/docs/configure_introduction.md
@@ -1,12 +1,12 @@
---
-title: Configure Introduction - Apache inlong
+title: Configure Introduction - Apache TubeMQ
---
-# inlong configuration item description
+# TubeMQ configuration item description
-The inlong server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, inlong. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separately.
+The TubeMQ server includes two modules for the Master and the Broker. The Master also includes a Web front-end module for external page access (this part is stored in the resources). Considering the actual deployment, two modules are often deployed in the same machine, TubeMQ. The contents of the three parts of the two modules are packaged and delivered to the operation and maintenance; the client does not include the lib package of the server part and is delivered to the user separately.
-Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the inlong-server-3.8.0/conf/ directory.
+Master and Broker use the ini configuration file format, and the relevant configuration files are placed in the master.ini and broker.ini files in the tubemq-server-3.8.0/conf/ directory.
Their configuration is defined by a set of configuration units. The Master configuration consists of four mandatory units: [master], [zookeeper], [bdbStore], and optional [tlsSetting]. The Broker configuration is mandatory. Broker], [zookeeper] and optional [tlsSetting] consist of a total of 3 configuration units; in actual use, you can also combine the contents of the two configuration files into one ini file.
@@ -46,7 +46,7 @@ In addition to the back-end system configuration file, the Master also stores th
| startConsumeAuthenticate | no | boolean | Whether to enable consumer user authentication, the default is false |
| startConsumeAuthorize | no | boolean | Whether to enable consumer consumption authorization authentication, the default is false |
| maxGroupBrokerConsumeRate | no | int | The maximum ratio of the number of clustered brokers to the number of members in the consumer group. The default is 50. In a 50-kerrow cluster, one consumer group is allowed to start at least one client. |
-| metaDataPath | no | string | Metadata storage path. Absolute, or relative to inlong base directory (`$BASE_DIR`). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior `0.5.0`. |
+| metaDataPath | no | string | Metadata storage path. Absolute, or relative to TubeMQ base directory (`$BASE_DIR`). Optional field, default is "var/meta_data". Should be the same as "[bdbStore].bdbEnvHome" if upgrade from version prior `0.5.0`. |
[zookeeper]
>The corresponding Tom MQ cluster of the Master stores the information about the ZooKeeper cluster of the Offset. The required unit has a fixed value of "[zookeeper]".
@@ -65,7 +65,7 @@ In addition to the back-end system configuration file, the Master also stores th
| Name | Required | Type | Description |
| ----------------------- | ----------------------------- | ----------------------------- | ------------------------------------------------------------ |
-| repGroupName | no | string | Cluster name, the primary and backup master node values must be the same. Optional field, default is "inlongMasterGroup". |
+| repGroupName | no | string | Cluster name, the primary and backup master node values must be the same. Optional field, default is "tubemqMasterGroup". |
| repNodeName | yes | string | The name of the master node in the cluster. The value of each node MUST BE DIFFERENT. Required field. |
| repNodePort | no | int | Node communication port, optional field, default is 9001. |
| repHelperHost | no | string | Primary node when the master cluster starts, optional field, default is "127.0.0.1:9001". |
diff --git a/en-us/docs/console_introduction.html b/en-us/docs/console_introduction.html
index 6fb16d6..bcfcad7 100644
--- a/en-us/docs/console_introduction.html
+++ b/en-us/docs/console_introduction.html
@@ -7,20 +7,20 @@
<meta name="keywords" content="console_introduction" />
<meta name="description" content="console_introduction" />
<!-- 网页标签标题 -->
- <title>Console Introduction - Apache inlong</title>
+ <title>Console Introduction - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<h2>管控台关系</h2>
-<p> inlong管控台是管理inlong集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与inlong系统相关的运营数据及操作。需要说明的是，当前提供的inlong前台所提供的功能没有涵盖inlong所提供的功能范围，大家可以参照《inlong HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。inlong管控台的访问地址为http://portal:webport/config/topic_list.htm：
+<p> TubeMQ管控台是管理TubeMQ集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与TubeMQ系统相关的运营数据及操作。需要说明的是，当前提供的TubeMQ前台所提供的功能没有涵盖TubeMQ所提供的功能范围，大家可以参照《TubeMQ HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。TubeMQ管控台的访问地址为http://portal:webport/config/topic_list.htm：
<img src="img/console/1568169770714.png" alt="">
其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。</p>
-<h2>inlong管控台各版面介绍</h2>
+<h2>TubeMQ管控台各版面介绍</h2>
<p> 管控台一共3项内容：分发查询，配置管理，集群管理；配置管理又分为Broker列表，Topic列表2个部分，我们先介绍简单的分发查询和集群管理，然后再介绍复杂的配置管理。</p>
<h3>分发查询</h3>
-<p> 点分发查询，我们会看到如下的列表信息，这是当前inlong集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
+<p> 点分发查询，我们会看到如下的列表信息，这是当前TubeMQ集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
<img src="img/console/1568169796122.png" alt="">
点击记录，可以看到选中的消费组里的消费者成员，及对应消费的Broker及Partition分区信息，如下图示：
<img src="img/console/1568169806810.png" alt=""></p>
@@ -32,16 +32,16 @@
<p> 配置管理版面既包含了Broker、Topic元数据的管理，还包含了Broker和Topic的上线发布以及下线操作，有2层含义，比如Broker列表里，展示的是当前集群里已配置的Broker元数据，包括未上线处于草稿状态、已上线、已下线的Broker记录信息：
<img src="img/console/1568169839931.png" alt=""></p>
<p> 从页面信息我们也可以看到，除了Broker的记录信息外，还有Broker在该集群里的管理信息，包括是否已上线，是否处于命令处理中，是否可读，是否可写，配置是否做了更改，是否已加载变更的配置信息。</p>
-<p> 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《inlong HTTP访问接口定义.xls》
+<p> 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《TubeMQ HTTP访问接口定义.xls》
<img src="img/console/1568169851085.png" alt=""></p>
-<p> 所有inlong管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。</p>
-<h2>inlong管控台上涉及的操作及注意事项</h2>
-<p> 如上所说，inlong管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类inlong集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：</p>
-<p> 1． <strong>inlong集群做扩缩容增、减Broker节点时，要先在inlong管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理</strong>：</p>
-<p> inlong集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。inlong管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确
认原因。目前该部分已经很成熟，出错信息会提 [...]
+<p> 所有TubeMQ管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。</p>
+<h2>TubeMQ管控台上涉及的操作及注意事项</h2>
+<p> 如上所说，TubeMQ管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类TubeMQ集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：</p>
+<p> 1． <strong>TubeMQ集群做扩缩容增、减Broker节点时，要先在TubeMQ管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理</strong>：</p>
+<p> TubeMQ集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。TubeMQ管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确
认原因。目前该部分已经很成熟，出错信息会提 [...]
<img src="img/console/1568169863402.png" alt="">
2． <strong>Topic元数据信息需要通过套件的业务使用界面进行新增和删除操作：</strong></p>
-<p> 如下图，业务发现自己消费的Topic在inlong管控台上没有，则需要在inlong的管控台上直接操作：
+<p> 如下图，业务发现自己消费的Topic在TubeMQ管控台上没有，则需要在TubeMQ的管控台上直接操作：
<img src="img/console/1568169879529.png" alt=""></p>
<p> 我们通过如上图中的Topic列表项完成Topic的新增，会弹出如下框，
<img src="img/console/1568169889594.png" alt=""></p>
diff --git a/en-us/docs/console_introduction.json b/en-us/docs/console_introduction.json
index 4ba683d..150552d 100644
--- a/en-us/docs/console_introduction.json
+++ b/en-us/docs/console_introduction.json
@@ -1,8 +1,8 @@
{
"filename": "console_introduction.md",
- "__html": "<h1>inlong管控台操作指引</h1>\n<h2>管控台关系</h2>\n<p> inlong管控台是管理inlong集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与inlong系统相关的运营数据及操作。需要说明的是，当前提供的inlong前台所提供的功能没有涵盖inlong所提供的功能范围，大家可以参照《inlong HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。inlong管控台的访问地址为http://portal:webport/config/topic_list.htm：\n<img src=\"img/console/1568169770714.png\" alt=\"\">\n 其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。</p>\n<h2>inlong管控台各版面介绍</h2>\n<p> 管控台一共3项内容：分发查询，配置管理，集群管理； [...]
+ "__html": "<h1>TubeMQ管控台操作指引</h1>\n<h2>管控台关系</h2>\n<p> TubeMQ管控台是管理TubeMQ集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与TubeMQ系统相关的运营数据及操作。需要说明的是，当前提供的TubeMQ前台所提供的功能没有涵盖TubeMQ所提供的功能范围，大家可以参照《TubeMQ HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。TubeMQ管控台的访问地址为http://portal:webport/config/topic_list.htm：\n<img src=\"img/console/1568169770714.png\" alt=\"\">\n 其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。</p>\n<h2>TubeMQ管控台各版面介绍</h2>\n<p> 管控台一共3项内容：分发查询，配置管理，集群管理； [...]
"link": "/en-us/docs/console_introduction.html",
"meta": {
- "title": "Console Introduction - Apache inlong"
+ "title": "Console Introduction - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/console_introduction.md b/en-us/docs/console_introduction.md
index 79b4c26..0ec9c20 100644
--- a/en-us/docs/console_introduction.md
+++ b/en-us/docs/console_introduction.md
@@ -1,23 +1,23 @@
---
-title: Console Introduction - Apache inlong
+title: Console Introduction - Apache TubeMQ
---
-# inlong管控台操作指引
+# TubeMQ管控台操作指引
## 管控台关系
- inlong管控台是管理inlong集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与inlong系统相关的运营数据及操作。需要说明的是，当前提供的inlong前台所提供的功能没有涵盖inlong所提供的功能范围，大家可以参照《inlong HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。inlong管控台的访问地址为http://portal:webport/config/topic_list.htm：
+ TubeMQ管控台是管理TubeMQ集群的简单运营工具，包括集群里的Master、Broker，以及Broker上部署的Topic元数据等与TubeMQ系统相关的运营数据及操作。需要说明的是，当前提供的TubeMQ前台所提供的功能没有涵盖TubeMQ所提供的功能范围，大家可以参照《TubeMQ HTTP访问接口定义.xls》定义自行实现符合业务需要的管控前台。TubeMQ管控台的访问地址为http://portal:webport/config/topic_list.htm：
其中portal为该集群中任意的主、备Master的IP地址，webport为配置的Master的Web端口。
-## inlong管控台各版面介绍
+## TubeMQ管控台各版面介绍
管控台一共3项内容：分发查询，配置管理，集群管理；配置管理又分为Broker列表，Topic列表2个部分，我们先介绍简单的分发查询和集群管理，然后再介绍复杂的配置管理。
### 分发查询
- 点分发查询，我们会看到如下的列表信息，这是当前inlong集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
+ 点分发查询，我们会看到如下的列表信息，这是当前TubeMQ集群里已注册的消费组信息，包括具体的消费组组名，消费的Topic，以及该组总的消费分区数简介信息，如下图示：
点击记录，可以看到选中的消费组里的消费者成员，及对应消费的Broker及Partition分区信息，如下图示：
@@ -36,22 +36,22 @@ title: Console Introduction - Apache inlong
从页面信息我们也可以看到，除了Broker的记录信息外，还有Broker在该集群里的管理信息，包括是否已上线，是否处于命令处理中，是否可读，是否可写，配置是否做了更改，是否已加载变更的配置信息。
- 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《inlong HTTP访问接口定义.xls》
+ 点单个新增，会弹框如下，这个表示待新增Broker的元数据信息，包括BrokerID，BrokerIP，BrokerPort，以及该Broker里部署的Topic的缺省配置信息，相关的字段详情见《TubeMQ HTTP访问接口定义.xls》
- 所有inlong管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
+ 所有TubeMQ管控台的变更操作，或者改变操作，都会要求输入操作授权码，该信息由运维通过Master的配置文件master.ini的confModAuthToken字段进行定义：如果你知道这个集群的密码，你就可以进行该项操作，比如你是管理员，你是授权人员，或者你能登陆这个master的机器拿到这个密码，都认为你是有权操作该项功能。
-## inlong管控台上涉及的操作及注意事项
+## TubeMQ管控台上涉及的操作及注意事项
- 如上所说，inlong管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类inlong集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
+ 如上所说，TubeMQ管控台是运营Tube MQ集群的，套件负责包括Master、Broker这类TubeMQ集群节点管理，包括自动部署和安装等，因此，如下几点需要注意：
- 1． **inlong集群做扩缩容增、减Broker节点时，要先在inlong管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
+ 1． **TubeMQ集群做扩缩容增、减Broker节点时，要先在TubeMQ管控台上做相应的节点新增、上线，以及下线、删除等操作后才能在物理环境上做对应Broker节点的增删处理**：
- inlong集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。inlong管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
+ TubeMQ集群对Broker按照状态机管理，如上图示涉及到[draft，online，read-only，write-only，offline] 等状态，记录增加还没生效时是draft状态，确定上线后是online态；节点删除首先要由online状态转为offline状态，然后再通过删除操作清理系统内保存的该节点记录；draft、online和offline是为了区分各个节点所处的环节，Master只将online状态的Broker分发给对应的producer和consumer进行生产和消费；read-only，write-only是Broker处于online状态的子状态，表示只能读或者只能写Broker上的数据；相关的状态及操作见页面详情，增加一条记录即可明白其中的关系。TubeMQ管控台上增加这些记录后，我们就可以进行Broker节点的部署及启动，这个时候Tube集群环境的页面会显示节点运行状态，如果为unregister状态，如下图示，则表示节点注册失败，需要到对应broker节点上检查日志，确认
原因。目前该部分已经很成熟，出错信息会提示完整 [...]
2． **Topic元数据信息需要通过套件的业务使用界面进行新增和删除操作：**
- 如下图，业务发现自己消费的Topic在inlong管控台上没有，则需要在inlong的管控台上直接操作：
+ 如下图，业务发现自己消费的Topic在TubeMQ管控台上没有，则需要在TubeMQ的管控台上直接操作：
我们通过如上图中的Topic列表项完成Topic的新增，会弹出如下框，
diff --git a/en-us/docs/consumer_example.html b/en-us/docs/consumer_example.html
index 788fd61..05c8a8d 100644
--- a/en-us/docs/consumer_example.html
+++ b/en-us/docs/consumer_example.html
@@ -7,13 +7,13 @@
<meta name="keywords" content="consumer_example" />
<meta name="description" content="consumer_example" />
<!-- 网页标签标题 -->
- <title>Consumer Example - Apache inlong</title>
+ <title>Consumer Example - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
<div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>inlong provides two ways to consumer message, PullConsumer and PushConsumer:</p>
+<p>TubeMQ provides two ways to consumer message, PullConsumer and PushConsumer:</p>
<ol>
<li>
<p>PullConsumer</p>
diff --git a/en-us/docs/consumer_example.json b/en-us/docs/consumer_example.json
index 5263e65..f01b8f6 100644
--- a/en-us/docs/consumer_example.json
+++ b/en-us/docs/consumer_example.json
@@ -1,8 +1,8 @@
{
"filename": "consumer_example.md",
- "__html": "<h2>Consumer Example</h2>\n<p>inlong provides two ways to consumer message, PullConsumer and PushConsumer:</p>\n<ol>\n<li>\n<p>PullConsumer</p>\n<pre><code class=\"language-java\"><span class=\"hljs-keyword\">public</span> <span class=\"hljs-class\"><span class=\"hljs-keyword\">class</span> <span class=\"hljs-title\">PullConsumerExample</span> </span>{\n\n <span class=\"hljs-function\"><span class=\"hljs-keyword\">public</span> <span class=\"hljs-keyword\">static</span> < [...]
+ "__html": "<h2>Consumer Example</h2>\n<p>TubeMQ provides two ways to consumer message, PullConsumer and PushConsumer:</p>\n<ol>\n<li>\n<p>PullConsumer</p>\n<pre><code class=\"language-java\"><span class=\"hljs-keyword\">public</span> <span class=\"hljs-class\"><span class=\"hljs-keyword\">class</span> <span class=\"hljs-title\">PullConsumerExample</span> </span>{\n\n <span class=\"hljs-function\"><span class=\"hljs-keyword\">public</span> <span class=\"hljs-keyword\">static</span> < [...]
"link": "/en-us/docs/consumer_example.html",
"meta": {
- "title": "Consumer Example - Apache inlong"
+ "title": "Consumer Example - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/consumer_example.md b/en-us/docs/consumer_example.md
index f40e764..8cc4cc7 100644
--- a/en-us/docs/consumer_example.md
+++ b/en-us/docs/consumer_example.md
@@ -1,9 +1,9 @@
---
-title: Consumer Example - Apache inlong
+title: Consumer Example - Apache TubeMQ
---
## Consumer Example
- inlong provides two ways to consumer message, PullConsumer and PushConsumer:
+ TubeMQ provides two ways to consumer message, PullConsumer and PushConsumer:
1. PullConsumer
```java
diff --git a/en-us/docs/contact.html b/en-us/docs/contact.html
index 210b64f..0a028d0 100644
--- a/en-us/docs/contact.html
+++ b/en-us/docs/contact.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="contact" />
<meta name="description" content="contact" />
<!-- 网页标签标题 -->
- <title>Contact Us - Apache inlong</title>
+ <title>Contact Us - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -28,20 +28,20 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="mailto:dev@inlong.apache.org">dev@inlong.apache.org</a></td>
+<td style="text-align:left"><a href="mailto:dev@tubemq.apache.org">dev@tubemq.apache.org</a></td>
<td style="text-align:left">Development-related discussions</td>
-<td style="text-align:left"><a href="mailto:dev-subscribe@inlong.apache.org">Subscribe</a></td>
-<td style="text-align:left"><a href="mailto:dev-unsubscribe@inlong.apache.org">Unsubscribe</a></td>
-<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/inlong-dev/">Archives</a></td>
+<td style="text-align:left"><a href="mailto:dev-subscribe@tubemq.apache.org">Subscribe</a></td>
+<td style="text-align:left"><a href="mailto:dev-unsubscribe@tubemq.apache.org">Unsubscribe</a></td>
+<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/tubemq-dev/">Archives</a></td>
</tr>
</tbody>
</table>
</li>
<li>
-<p>Home page: <a href="https://inlong.apache.org">https://inlong.apache.org</a></p>
+<p>Home page: <a href="https://tubemq.apache.org">https://tubemq.apache.org</a></p>
</li>
<li>
-<p>Issues: <a href="https://issues.apache.org/jira/browse/inlong">https://issues.apache.org/jira/browse/inlong</a></p>
+<p>Issues: <a href="https://issues.apache.org/jira/browse/TubeMQ">https://issues.apache.org/jira/browse/TubeMQ</a></p>
</li>
</ul>
<h2>License</h2>
diff --git a/en-us/docs/contact.json b/en-us/docs/contact.json
index 211ae5d..8b41ba8 100644
--- a/en-us/docs/contact.json
+++ b/en-us/docs/contact.json
@@ -1,8 +1,8 @@
{
"filename": "contact.md",
- "__html": "<h2>Contact us</h2>\n<ul>\n<li>\n<p>Mailing lists</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@inlong.apache.org\">dev@inlong.apache.org</a></td>\n<td style=\"text-align:left\">Development-related discussions</td>\n<td [...]
+ "__html": "<h2>Contact us</h2>\n<ul>\n<li>\n<p>Mailing lists</p>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">Name</th>\n<th style=\"text-align:left\">Scope</th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n<th style=\"text-align:left\"></th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:left\"><a href=\"mailto:dev@tubemq.apache.org\">dev@tubemq.apache.org</a></td>\n<td style=\"text-align:left\">Development-related discussions</td>\n<td [...]
"link": "/en-us/docs/contact.html",
"meta": {
- "title": "Contact Us - Apache inlong"
+ "title": "Contact Us - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/contact.md b/en-us/docs/contact.md
index 4fa3ac1..35b693c 100644
--- a/en-us/docs/contact.md
+++ b/en-us/docs/contact.md
@@ -1,5 +1,5 @@
---
-title: Contact Us - Apache inlong
+title: Contact Us - Apache TubeMQ
---
Contact us
@@ -9,10 +9,10 @@ Contact us
| Name | Scope | | | |
|:------------------------------------------------------------------------------|:--------------------------------|:----------------------------------------------------------------|:--------------------------------------------------------------------|:-----------------------------------------------------------------------------|
- | [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@inlong.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@inlong.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/inlong-dev/) |
+ | [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | Development-related discussions | [Subscribe](mailto:dev-subscribe@tubemq.apache.org) | [Unsubscribe](mailto:dev-unsubscribe@tubemq.apache.org) | [Archives](http://mail-archives.apache.org/mod_mbox/tubemq-dev/) |
-- Home page: https://inlong.apache.org
-- Issues: https://issues.apache.org/jira/browse/inlong
+- Home page: https://tubemq.apache.org
+- Issues: https://issues.apache.org/jira/browse/TubeMQ
diff --git a/en-us/docs/deployment.html b/en-us/docs/deployment.html
index 2ad5866..cc0b43b 100644
--- a/en-us/docs/deployment.html
+++ b/en-us/docs/deployment.html
@@ -7,23 +7,23 @@
<meta name="keywords" content="deployment" />
<meta name="description" content="deployment" />
<!-- 网页标签标题 -->
- <title>Deployment - Apache inlong</title>
+ <title>Deployment - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<h2>Compile and Package Project：</h2>
<p>Enter the root directory of project and run:</p>
<pre><code>mvn clean package -Dmaven.test.skip
</code></pre>
-<p>e.g. We put the inlong project package at <code>E:/</code>, then run the above command. Compilation is complete when all subdirectories are compiled successfully.</p>
+<p>e.g. We put the TubeMQ project package at <code>E:/</code>, then run the above command. Compilation is complete when all subdirectories are compiled successfully.</p>
<p><img src="img/sysdeployment/sys_compile.png" alt=""></p>
<p>We can also run individual compilation in each subdirectory. Steps are the same as the whole project's compilation.</p>
<p><strong>Server Deployment</strong></p>
-<p>As example above, entry directory <code>E:\GIT\inlong\inlong-server\target</code>, we can see several JARs. <code>inlong-server-3.8.0-bin.tar.gz</code> is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. <code>inlong-server-3.8.0.jar</code> is a server-side processing package included in <code>lib</code> of the complete project installer. Consider to daily changes and upgrades are most made to serv [...]
+<p>As example above, entry directory <code>E:\GIT\TubeMQ\tubemq-server\target</code>, we can see several JARs. <code>tubemq-server-3.8.0-bin.tar.gz</code> is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. <code>tubemq-server-3.8.0.jar</code> is a server-side processing package included in <code>lib</code> of the complete project installer. Consider to daily changes and upgrades are most made to serv [...]
<p><img src="img/sysdeployment/sys_package.png" alt=""></p>
-<p>Here we have a complete package deployed onto server and we place it in <code>/data/inlong</code></p>
+<p>Here we have a complete package deployed onto server and we place it in <code>/data/tubemq</code></p>
<p><img src="img/sysdeployment/sys_package_list.png" alt=""></p>
<p><strong>Configuration System</strong></p>
<p>There are 3 roles in server package: Master, Broker and Tools. Master and Broker can be deployed on the same or different machine. It depends on the bussiness layouts. As example below, we have 3 machine to startup a complete production and consumption cluster with 2 Masters.</p>
@@ -61,7 +61,7 @@
<td>2181</td>
<td></td>
<td></td>
-<td>Offset stored at root directory<code>/inlong</code></td>
+<td>Offset stored at root directory<code>/tubemq</code></td>
</tr>
<tr>
<td>100.115.158.208</td>
@@ -124,7 +124,7 @@
<p>Visiting Master's Administrator panel(<a href="http://100.115.158.208:8080/config/topic_list.htm">http://100.115.158.208:8080/config/topic_list.htm</a>), search operation working well indicates that master has been successfully started up.</p>
<p><img src="img/sysdeployment/sys_master_console.png" alt=""></p>
<p><strong>Start up Broker</strong>：</p>
-<p>Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire inlong cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.</p>
+<p>Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire TubeMQ cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.</p>
<p><img src="img/sysdeployment/sys_broker_configure.png" alt=""></p>
<p>Confirm and create a draft record of Broker.</p>
<p><img src="img/sysdeployment/sys_broker_online.png" alt=""></p>
@@ -143,7 +143,7 @@
<p><img src="img/sysdeployment/sys_broker_finished.png" alt=""></p>
<p><strong>Topic Configuration and Activation</strong>：</p>
<p>Configuration of Topic is similar with Broker's, we should add metadata on Master before using them, otherwise it will report an Not Found Error during production/consumption. For example, if we try to consum a non-existent topic <code>test</code>,</p>
-<pre><code>/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+<pre><code>/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
</code></pre>
<p>Demo returns error message.</p>
<p><img src="img/sysdeployment/sys_topic_error.png" alt=""></p>
@@ -156,20 +156,20 @@
<p><img src="img/sysdeployment/sys_topic_finished.png" alt=""></p>
<p><strong>Note</strong> When we are executing overload opertaion, we should make it in batches. Overload operations are controlled by state machines. It would become unwritable and un readale, read-only, readable and writable in order before published. Waiting for overloads on all brokers make topic temporary unreadable and unwritable, which result in production and consumption failure, especially production failure.</p>
<p><strong>Message Production and Consumption</strong>：</p>
-<p>We pack Demo for test in package or <code>inlong-client-3.8.0.jar</code> can be used for implementing your own production and consumption.
+<p>We pack Demo for test in package or <code>tubemq-client-3.8.0.jar</code> can be used for implementing your own production and consumption.
We run Producer Demo in below script and we can see data accepted on Broker.</p>
-<pre><code>/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+<pre><code>/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
</code></pre>
<p><img src="img/sysdeployment/sys_node_status.png" alt=""></p>
<p>Then we run the Consumption Demo and we can see that consumption is also working properly.</p>
-<pre><code> /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
+<pre><code> /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
</code></pre>
<p><img src="img/sysdeployment/sys_node_status_2.png" alt=""></p>
<p>As we can see, files relative to broker's production and consumption already exist.</p>
<p><img src="img/sysdeployment/sys_node_log.png" alt=""></p>
-<p>Here, the compilation, deployment, system configuration, startup, production and consumption of inlong has been completed!
-If you need to get further, please refer to "inlong HTTP API" and make your appropriate configuration settings.</p>
+<p>Here, the compilation, deployment, system configuration, startup, production and consumption of TubeMQ has been completed!
+If you need to get further, please refer to "TubeMQ HTTP API" and make your appropriate configuration settings.</p>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
<script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
diff --git a/en-us/docs/deployment.json b/en-us/docs/deployment.json
index c2ff247..abf6d63 100644
--- a/en-us/docs/deployment.json
+++ b/en-us/docs/deployment.json
@@ -1,8 +1,8 @@
{
"filename": "deployment.md",
- "__html": "<h1>Compile, Deploy and Examples of inlong ：</h1>\n<h2>Compile and Package Project：</h2>\n<p>Enter the root directory of project and run:</p>\n<pre><code>mvn clean package -Dmaven.test.skip\n</code></pre>\n<p>e.g. We put the inlong project package at <code>E:/</code>, then run the above command. Compilation is complete when all subdirectories are compiled successfully.</p>\n<p><img src=\"img/sysdeployment/sys_compile.png\" alt=\"\"></p>\n<p>We can also run individual compila [...]
+ "__html": "<h1>Compile, Deploy and Examples of TubeMQ ：</h1>\n<h2>Compile and Package Project：</h2>\n<p>Enter the root directory of project and run:</p>\n<pre><code>mvn clean package -Dmaven.test.skip\n</code></pre>\n<p>e.g. We put the TubeMQ project package at <code>E:/</code>, then run the above command. Compilation is complete when all subdirectories are compiled successfully.</p>\n<p><img src=\"img/sysdeployment/sys_compile.png\" alt=\"\"></p>\n<p>We can also run individual compila [...]
"link": "/en-us/docs/deployment.html",
"meta": {
- "title": "Deployment - Apache inlong"
+ "title": "Deployment - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/deployment.md b/en-us/docs/deployment.md
index 32ac11f..2a7b257 100644
--- a/en-us/docs/deployment.md
+++ b/en-us/docs/deployment.md
@@ -1,8 +1,8 @@
---
-title: Deployment - Apache inlong
+title: Deployment - Apache TubeMQ
---
-# Compile, Deploy and Examples of inlong ：
+# Compile, Deploy and Examples of TubeMQ ：
## Compile and Package Project：
@@ -12,7 +12,7 @@ Enter the root directory of project and run:
mvn clean package -Dmaven.test.skip
```
-e.g. We put the inlong project package at `E:/`, then run the above command. Compilation is complete when all subdirectories are compiled successfully.
+e.g. We put the TubeMQ project package at `E:/`, then run the above command. Compilation is complete when all subdirectories are compiled successfully.
@@ -20,12 +20,12 @@ We can also run individual compilation in each subdirectory. Steps are the same
**Server Deployment**
-As example above, entry directory `E:\GIT\inlong\inlong-server\target`, we can see several JARs. `inlong-server-3.8.0-bin.tar.gz` is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. `inlong-server-3.8.0.jar` is a server-side processing package included in `lib` of the complete project installer. Consider to daily changes and upgrades are most made to server side, we place this jar separately so that w [...]
+As example above, entry directory `E:\GIT\TubeMQ\tubemq-server\target`, we can see several JARs. `tubemq-server-3.8.0-bin.tar.gz` is the complete server-side installation package， including execution scripts, configuration files, dependencies, and frontend source code. `tubemq-server-3.8.0.jar` is a server-side processing package included in `lib` of the complete project installer. Consider to daily changes and upgrades are most made to server side, we place this jar separately so that w [...]
-Here we have a complete package deployed onto server and we place it in `/data/inlong`
+Here we have a complete package deployed onto server and we place it in `/data/tubemq`
@@ -38,7 +38,7 @@ There are 3 roles in server package: Master, Broker and Tools. Master and Broker
| --- | --- | --- | --- | --- | --- |
| 10.224.148.145 | **Master** | 8099 | 8199 | 8080 | Metadata stored at `/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | Message stored at`/stage/msgdata` |
-| | ZK | 2181 | | | Offset stored at root directory`/inlong` |
+| | ZK | 2181 | | | Offset stored at root directory`/tubemq` |
| 100.115.158.208 | **Master** | 8099 | 8199 | 8080 | Metadata stored at `/stage/metadata` |
| | Broker | 8123 | 8124 | 8081 | Message stored at`/stage/msgdata` |
| 10.224.155.80 | Producer ||||
@@ -78,7 +78,7 @@ Visiting Master's Administrator panel([http://100.115.158.208:8080/config/topic\
**Start up Broker**：
-Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire inlong cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.
+Starting up Broker is a little bit different to starting Master: Master is responsible for managing the entire TubeMQ cluster, including Broker node with Topic configuration on them, production and consumption managament. So we need to add metadata on Master before starting up Broker.
@@ -118,7 +118,7 @@ Check the Master Control Panel, broker has successfully registered.
Configuration of Topic is similar with Broker's, we should add metadata on Master before using them, otherwise it will report an Not Found Error during production/consumption. For example, if we try to consum a non-existent topic `test`,
```
-/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
Demo returns error message.
@@ -144,17 +144,17 @@ Topic is available after overload. We can see some status of topic has changed a
**Message Production and Consumption**：
-We pack Demo for test in package or `inlong-client-3.8.0.jar` can be used for implementing your own production and consumption.
+We pack Demo for test in package or `tubemq-client-3.8.0.jar` can be used for implementing your own production and consumption.
We run Producer Demo in below script and we can see data accepted on Broker.
```
-/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
+/usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageProducerExample 100.115.158.208 10.224.148.145:8000,100.115.158.208:8000 test 10000000
```
Then we run the Consumption Demo and we can see that consumption is also working properly.
```
- /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/inlong/inlong-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/inlong/inlong-server-3.8.0/lib/\*:/data/inlong/inlong-server-3.8.0/conf/\*: com.tencent.inlong.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
+ /usr/local/java/default/bin/java -Xmx512m -Dlog4j.configuration=file:/data/tubemq/tubemq-server-3.8.0/conf/tools.log4j.properties -Djava.net.preferIPv4Stack=true -cp /data/tubemq/tubemq-server-3.8.0/lib/\*:/data/tubemq/tubemq-server-3.8.0/conf/\*: com.tencent.tubemq.example.MessageConsumerExample 10.224.148.145 10.224.148.145:8000,100.115.158.208:8000 test testGroup 3 1 1
```
@@ -164,5 +164,5 @@ As we can see, files relative to broker's production and consumption already exi
-Here, the compilation, deployment, system configuration, startup, production and consumption of inlong has been completed!
-If you need to get further, please refer to "inlong HTTP API" and make your appropriate configuration settings.
\ No newline at end of file
+Here, the compilation, deployment, system configuration, startup, production and consumption of TubeMQ has been completed!
+If you need to get further, please refer to "TubeMQ HTTP API" and make your appropriate configuration settings.
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-become-a-committer.html b/en-us/docs/development/how-to-become-a-committer.html
index b7fa924..a3ef5c9 100644
--- a/en-us/docs/development/how-to-become-a-committer.html
+++ b/en-us/docs/development/how-to-become-a-committer.html
@@ -7,24 +7,24 @@
<meta name="keywords" content="how-to-become-a-committer" />
<meta name="description" content="how-to-become-a-committer" />
<!-- 网页标签标题 -->
- <title>How to Become a Committer - Apache InLong</title>
+ <title>How to Become a Committer - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<blockquote>
-<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
-Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>
+<p>Apache TubeMQ是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
+Apache TubeMQ Committer拥有TubeMQ代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache TubeMQ Committer。</p>
</blockquote>
-<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
+<p>任何人只要对TubeMQ项目做了贡献，那你就是官方承认的TubeMQ项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，
或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。</p>
<p>潜在贡献清单（无特定顺序）：</p>
<ul>
<li>提交自己发现的Bug、特性、改进到issue</li>
-<li>更新官方文档使项目的文档是最近的、撰写InLong的最佳实践、特性剖析的各种对用户有用的文档</li>
+<li>更新官方文档使项目的文档是最近的、撰写TubeMQ的最佳实践、特性剖析的各种对用户有用的文档</li>
<li>执行测试并报告测试结果，性能测试与其他MQ的性能对比测试等</li>
<li>发布版本时，积极参与投票</li>
<li>参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件</li>
@@ -32,16 +32,16 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
<li>审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议</li>
<li>对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等</li>
<li>指导新加入的贡献者，熟悉社区流程</li>
-<li>发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站</li>
-<li>有利于InLong社区发展的任何贡献</li>
+<li>发表关于TubeMQ的演讲和博客，并将这些添加到TubeMQ的官方网站</li>
+<li>有利于TubeMQ社区发展的任何贡献</li>
<li>......</li>
</ul>
<p>更多可以参考：<a href="https://community.apache.org/contributors/">ASF官方文档</a></p>
<p>并不是每个人都能完成这个清单上的所有（甚至任何）项目。如果你想用其他方式来做贡献，那就去做吧（并把它们添加到列表中）。
-愉快的举止和乐于奉献的精神是您对InLong项目产生积极影响所需要的全部。
-邀请您成为Committer是您与社区长期稳定互动的结果，是InLong社区对您的信任和认可。</p>
+愉快的举止和乐于奉献的精神是您对TubeMQ项目产生积极影响所需要的全部。
+邀请您成为Committer是您与社区长期稳定互动的结果，是TubeMQ社区对您的信任和认可。</p>
<p>Committer有义务审查(Review)和合并(merge)其他人提交的PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
-当你足够活跃且对社区的贡献比较大后，就可以晋升为InLong项目的PPMC成员。</p>
+当你足够活跃且对社区的贡献比较大后，就可以晋升为TubeMQ项目的PPMC成员。</p>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
<script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
diff --git a/en-us/docs/development/how-to-become-a-committer.json b/en-us/docs/development/how-to-become-a-committer.json
index b081063..7db6aea 100644
--- a/en-us/docs/development/how-to-become-a-committer.json
+++ b/en-us/docs/development/how-to-become-a-committer.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-become-a-committer.md",
- "__html": "<h1>如何成为Apache InLong Committer 和 PPMC</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。</p>\n</blockquote>\n<p>任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Comm [...]
+ "__html": "<h1>如何成为Apache TubeMQ Committer 和 PPMC</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>Apache TubeMQ是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，\nApache TubeMQ Committer拥有TubeMQ代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache TubeMQ Committer。</p>\n</blockquote>\n<p>任何人只要对TubeMQ项目做了贡献，那你就是官方承认的TubeMQ项目的Contributor了，从Contributor成长为Comm [...]
"link": "/en-us/docs/development/how-to-become-a-committer.html",
"meta": {
- "title": "How to Become a Committer - Apache InLong"
+ "title": "How to Become a Committer - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-become-a-committer.md b/en-us/docs/development/how-to-become-a-committer.md
index 521f704..df8bc75 100644
--- a/en-us/docs/development/how-to-become-a-committer.md
+++ b/en-us/docs/development/how-to-become-a-committer.md
@@ -1,21 +1,21 @@
---
-title: How to Become a Committer - Apache InLong
+title: How to Become a Committer - Apache TubeMQ
---
-# 如何成为Apache InLong Committer 和 PPMC
+# 如何成为Apache TubeMQ Committer 和 PPMC
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
-> Apache InLong是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
-Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache InLong Committer。
+> Apache TubeMQ是完全按照Apache的规则来构建社区的，Apache Committer是ASF（Apache软件基金会）中用来表示提交特定项目的人的术语，
+Apache TubeMQ Committer拥有TubeMQ代码库的写权限，可以合并PR，任何人只要为社区做出了足够的贡献并获取到足够的信任就可以成为Apache TubeMQ Committer。
-任何人只要对InLong项目做了贡献，那你就是官方承认的InLong项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
+任何人只要对TubeMQ项目做了贡献，那你就是官方承认的TubeMQ项目的Contributor了，从Contributor成长为Committer并没有一个确切的标准，
也没有任何预期的时间表，但是Committer的候选人一般都是长期活跃的贡献者，成为Committer并没有要求必须有巨大的架构改进贡献，
或者多少行的代码贡献，贡献代码、贡献文档、参与邮件列表的讨论、帮助回答问题等等都提升自己影响力的方式。
潜在贡献清单（无特定顺序）：
- 提交自己发现的Bug、特性、改进到issue
-- 更新官方文档使项目的文档是最近的、撰写InLong的最佳实践、特性剖析的各种对用户有用的文档
+- 更新官方文档使项目的文档是最近的、撰写TubeMQ的最佳实践、特性剖析的各种对用户有用的文档
- 执行测试并报告测试结果，性能测试与其他MQ的性能对比测试等
- 发布版本时，积极参与投票
- 参与邮件列表中的讨论，一般会有以[DISCUSS]开头的邮件
@@ -23,15 +23,15 @@ Apache InLong Committer拥有InLong代码库的写权限，可以合并PR，任
- 审查(Review)其他人的工作（包括代码和非代码）并发表你自己的建议
- 对JIRA上的issue进行审查，维护issue为最新状态，比如：关闭过时的issue、更改issue的错误信息等
- 指导新加入的贡献者，熟悉社区流程
-- 发表关于InLong的演讲和博客，并将这些添加到InLong的官方网站
-- 有利于InLong社区发展的任何贡献
+- 发表关于TubeMQ的演讲和博客，并将这些添加到TubeMQ的官方网站
+- 有利于TubeMQ社区发展的任何贡献
- ......
更多可以参考：[ASF官方文档](https://community.apache.org/contributors/)
并不是每个人都能完成这个清单上的所有（甚至任何）项目。如果你想用其他方式来做贡献，那就去做吧（并把它们添加到列表中）。
-愉快的举止和乐于奉献的精神是您对InLong项目产生积极影响所需要的全部。
-邀请您成为Committer是您与社区长期稳定互动的结果，是InLong社区对您的信任和认可。
+愉快的举止和乐于奉献的精神是您对TubeMQ项目产生积极影响所需要的全部。
+邀请您成为Committer是您与社区长期稳定互动的结果，是TubeMQ社区对您的信任和认可。
Committer有义务审查(Review)和合并(merge)其他人提交的PR，版本发布时测试和投票候选版本，参与特性设计方案的讨论以及其他类型的项目贡献。
-当你足够活跃且对社区的贡献比较大后，就可以晋升为InLong项目的PPMC成员。
+当你足够活跃且对社区的贡献比较大后，就可以晋升为TubeMQ项目的PPMC成员。
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-commit.html b/en-us/docs/development/how-to-commit.html
index 2df4227..f009cc0 100644
--- a/en-us/docs/development/how-to-commit.html
+++ b/en-us/docs/development/how-to-commit.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="how-to-commit" />
<meta name="description" content="how-to-commit" />
<!-- 网页标签标题 -->
- <title>How to Commit - Apache InLong</title>
+ <title>How to Commit - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -15,33 +15,33 @@
<div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<h2>0. 前言</h2>
-<p>Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。</p>
+<p>Apache TubeMQ使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。</p>
<ul>
<li>
-<p>InLong代码库：<a href="https://github.com/apache/incubator-inlong">https://github.com/apache/incubator-inlong</a></p>
+<p>TubeMQ代码库：<a href="https://github.com/apache/incubator-tubemq">https://github.com/apache/incubator-tubemq</a></p>
</li>
<li>
-<p>InLong官网库：<a href="https://github.com/apache/incubator-inlong-website">https://github.com/apache/incubator-inlong-website</a></p>
+<p>TubeMQ官网库：<a href="https://github.com/apache/incubator-tubemq-website">https://github.com/apache/incubator-tubemq-website</a></p>
</li>
</ul>
<h2>1. Fork仓库</h2>
-<p>进入 <a href="https://github.com/apache/incubator-inlong">apache/incubator-inlong</a> 的Github页面 ，点击右上角按钮 <code>Fork</code> 进行 Fork。如下图所示：</p>
+<p>进入 <a href="https://github.com/apache/incubator-tubemq">apache/incubator-tubemq</a> 的Github页面 ，点击右上角按钮 <code>Fork</code> 进行 Fork。如下图所示：</p>
<p><img src="../img/development/github_fork_repository.png" alt=""></p>
<h2>2. 配置git和提交修改</h2>
<h3>2.1 将代码克隆到本地</h3>
-<pre><code class="language-shell">git clone https://github.com/<your_github_name>/incubator-inlong.git
+<pre><code class="language-shell">git clone https://github.com/<your_github_name>/incubator-tubemq.git
</code></pre>
<p>clone完成后，origin会默认指向github上的远程fork地址。</p>
-<h3>2.2 将 apache/incubator-inlong 添加为本地仓库的远程分支upstream</h3>
-<pre><code class="language-shell">cd incubator-inlong
-git remote add upstream https://github.com/apache/incubator-inlong.git
+<h3>2.2 将 apache/incubator-tubemq 添加为本地仓库的远程分支upstream</h3>
+<pre><code class="language-shell">cd incubator-tubemq
+git remote add upstream https://github.com/apache/incubator-tubemq.git
</code></pre>
<h3>2.3 检查远程仓库设置</h3>
<pre><code class="language-shell">git remote -v
-origin https://github.com/<your_github_name>/incubator-inlong.git (fetch)
-origin https://github.com/<your_github_name>/incubator-inlong.git(push)
-upstream https://github.com/apache/incubator-inlong.git (fetch)
-upstream https://github.com/apache/incubator-inlong.git (push)
+origin https://github.com/<your_github_name>/incubator-tubemq.git (fetch)
+origin https://github.com/<your_github_name>/incubator-tubemq.git(push)
+upstream https://github.com/apache/incubator-tubemq.git (fetch)
+upstream https://github.com/apache/incubator-tubemq.git (push)
</code></pre>
<p>此时会有两个仓库：origin(自己的仓库)和upstream（官方的仓库）</p>
<h3>2.4 获取upstream仓库代码，并更新本地master分支代码为最新</h3>
@@ -50,25 +50,25 @@ git pull upstream master
</code></pre>
<h3>2.5 新建分支</h3>
<blockquote>
-<p>一般以issue id作为分支名，如：InLong-123</p>
+<p>一般以issue id作为分支名，如：TUBEMQ-123</p>
</blockquote>
-<pre><code class="language-shell">git checkout -b InLong-123
+<pre><code class="language-shell">git checkout -b TUBEMQ-123
</code></pre>
-<p><strong>确保分支<code>InLong-123</code>是基于官方master分支的最新代码</strong></p>
+<p><strong>确保分支<code>TUBEMQ-123</code>是基于官方master分支的最新代码</strong></p>
<p>分支创建完成后即可进行代码更改。</p>
<h3>2.6 提交代码到远程分支</h3>
<blockquote>
-<p>commit 信息的格式必须与Issue标题保持一致且以<code>[issue id]</code>开头，即：<code>[InLong-123] xxx</code></p>
+<p>commit 信息的格式必须与Issue标题保持一致且以<code>[issue id]</code>开头，即：<code>[TUBEMQ-123] xxx</code></p>
</blockquote>
-<pre><code class="language-shell">git commit -a -m "[InLong-123] xxx"
-git push origin InLong-123
+<pre><code class="language-shell">git commit -a -m "[TUBEMQ-123] xxx"
+git push origin TUBEMQ-123
</code></pre>
<h2>3. 创建PR</h2>
<h3>3.1 打开自己的github仓库页面</h3>
-<pre><code>`https://github.com/<your_github_name>/incubator-inlong`
+<pre><code>`https://github.com/<your_github_name>/incubator-tubemq`
</code></pre>
<h3>3.2. 切换分支</h3>
-<pre><code>切换到提交的分支 `InLong-123`
+<pre><code>切换到提交的分支 `TUBEMQ-123`
</code></pre>
<h3>3.3. 创建新PR</h3>
<pre><code>点击 `New pull request`或者`Compare & pull request`
@@ -78,14 +78,14 @@ git push origin InLong-123
<pre><code>需要注意以下几点：
1. PR的标题必须以issue id开头，最好与commit信息保持一致
2. 可以填写部分描述信息也可以不填
- 3. 如果点击`Create pull request`后提示代码冲突，则请将`InLong-123`分支的代码
+ 3. 如果点击`Create pull request`后提示代码冲突，则请将`TUBEMQ-123`分支的代码
与master分支同步一致后在进行提交
</code></pre>
<p><img src="../img/development/create_pull_request.png" alt=""></p>
<h2>4. Review代码</h2>
<p>创建完PR后，所有的人都可以Review代码，可能会与您讨论一些实现的细节，可能还需要你进一步修改。
<strong>一般该PR必须有2位以上的社区PPMC/Committer +1后，才可能正式合入官方代码库。</strong></p>
-<p>最后，恭喜您已经成为了InLong的官方贡献者了！</p>
+<p>最后，恭喜您已经成为了TubeMQ的官方贡献者了！</p>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
<script src="https://f.alicdn.com/react/15.4.1/react-dom.min.js"></script>
diff --git a/en-us/docs/development/how-to-commit.json b/en-us/docs/development/how-to-commit.json
index 50378ca..063be8e 100644
--- a/en-us/docs/development/how-to-commit.json
+++ b/en-us/docs/development/how-to-commit.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-commit.md",
- "__html": "<h1>如何提交代码</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>0. 前言</h2>\n<p>Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。</p>\n<ul>\n<li>\n<p>InLong代码库：<a href=\"https://github.com/apache/incubator-inlong\">https://github.com/apache/incubator-inlong</a></p>\n</li>\n<li>\n<p>InLong官网库：<a href=\"https://github.com/apache/incubator-inlong-website\">https://githu [...]
+ "__html": "<h1>如何提交代码</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>0. 前言</h2>\n<p>Apache TubeMQ使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。</p>\n<ul>\n<li>\n<p>TubeMQ代码库：<a href=\"https://github.com/apache/incubator-tubemq\">https://github.com/apache/incubator-tubemq</a></p>\n</li>\n<li>\n<p>TubeMQ官网库：<a href=\"https://github.com/apache/incubator-tubemq-website\">https://githu [...]
"link": "/en-us/docs/development/how-to-commit.html",
"meta": {
- "title": "How to Commit - Apache InLong"
+ "title": "How to Commit - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-commit.md b/en-us/docs/development/how-to-commit.md
index 9c1fc74..89022d4 100644
--- a/en-us/docs/development/how-to-commit.md
+++ b/en-us/docs/development/how-to-commit.md
@@ -1,5 +1,5 @@
---
-title: How to Commit - Apache InLong
+title: How to Commit - Apache TubeMQ
---
# 如何提交代码
@@ -7,15 +7,15 @@ title: How to Commit - Apache InLong
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
## 0. 前言
-Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
+Apache TubeMQ使用Github的Pull Request (PR)来接收贡献的代码，本文将详细介绍提交代码的详细流程。
-- InLong代码库：https://github.com/apache/incubator-inlong
+- TubeMQ代码库：https://github.com/apache/incubator-tubemq
-- InLong官网库：https://github.com/apache/incubator-inlong-website
+- TubeMQ官网库：https://github.com/apache/incubator-tubemq-website
## 1. Fork仓库
-进入 [apache/incubator-inlong](https://github.com/apache/incubator-inlong) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
+进入 [apache/incubator-tubemq](https://github.com/apache/incubator-tubemq) 的Github页面 ，点击右上角按钮 `Fork` 进行 Fork。如下图所示：
@@ -23,22 +23,22 @@ Apache InLong使用Github的Pull Request (PR)来接收贡献的代码，本文
### 2.1 将代码克隆到本地
```shell
-git clone https://github.com/<your_github_name>/incubator-inlong.git
+git clone https://github.com/<your_github_name>/incubator-tubemq.git
```
clone完成后，origin会默认指向github上的远程fork地址。
-### 2.2 将 apache/incubator-inlong 添加为本地仓库的远程分支upstream
+### 2.2 将 apache/incubator-tubemq 添加为本地仓库的远程分支upstream
```shell
-cd incubator-inlong
-git remote add upstream https://github.com/apache/incubator-inlong.git
+cd incubator-tubemq
+git remote add upstream https://github.com/apache/incubator-tubemq.git
```
### 2.3 检查远程仓库设置
```shell
git remote -v
-origin https://github.com/<your_github_name>/incubator-inlong.git (fetch)
-origin https://github.com/<your_github_name>/incubator-inlong.git(push)
-upstream https://github.com/apache/incubator-inlong.git (fetch)
-upstream https://github.com/apache/incubator-inlong.git (push)
+origin https://github.com/<your_github_name>/incubator-tubemq.git (fetch)
+origin https://github.com/<your_github_name>/incubator-tubemq.git(push)
+upstream https://github.com/apache/incubator-tubemq.git (fetch)
+upstream https://github.com/apache/incubator-tubemq.git (push)
```
此时会有两个仓库：origin(自己的仓库)和upstream（官方的仓库）
@@ -48,25 +48,25 @@ git fetch upstream
git pull upstream master
```
### 2.5 新建分支
-> 一般以issue id作为分支名，如：InLong-123
+> 一般以issue id作为分支名，如：TUBEMQ-123
```shell
-git checkout -b InLong-123
+git checkout -b TUBEMQ-123
```
-**确保分支`InLong-123`是基于官方master分支的最新代码**
+**确保分支`TUBEMQ-123`是基于官方master分支的最新代码**
分支创建完成后即可进行代码更改。
### 2.6 提交代码到远程分支
-> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[InLong-123] xxx`
+> commit 信息的格式必须与Issue标题保持一致且以`[issue id]`开头，即：`[TUBEMQ-123] xxx`
```shell
-git commit -a -m "[InLong-123] xxx"
-git push origin InLong-123
+git commit -a -m "[TUBEMQ-123] xxx"
+git push origin TUBEMQ-123
```
## 3. 创建PR
### 3.1 打开自己的github仓库页面
- `https://github.com/<your_github_name>/incubator-inlong`
+ `https://github.com/<your_github_name>/incubator-tubemq`
### 3.2. 切换分支
- 切换到提交的分支 `InLong-123`
+ 切换到提交的分支 `TUBEMQ-123`
### 3.3. 创建新PR
点击 `New pull request`或者`Compare & pull request`
@@ -74,7 +74,7 @@ git push origin InLong-123
需要注意以下几点：
1. PR的标题必须以issue id开头，最好与commit信息保持一致
2. 可以填写部分描述信息也可以不填
- 3. 如果点击`Create pull request`后提示代码冲突，则请将`InLong-123`分支的代码
+ 3. 如果点击`Create pull request`后提示代码冲突，则请将`TUBEMQ-123`分支的代码
与master分支同步一致后在进行提交
@@ -83,4 +83,4 @@ git push origin InLong-123
创建完PR后，所有的人都可以Review代码，可能会与您讨论一些实现的细节，可能还需要你进一步修改。
**一般该PR必须有2位以上的社区PPMC/Committer +1后，才可能正式合入官方代码库。**
-最后，恭喜您已经成为了InLong的官方贡献者了！
+最后，恭喜您已经成为了TubeMQ的官方贡献者了！
diff --git a/en-us/docs/development/how-to-contribute.html b/en-us/docs/development/how-to-contribute.html
index f84cdf1..2393692 100644
--- a/en-us/docs/development/how-to-contribute.html
+++ b/en-us/docs/development/how-to-contribute.html
@@ -7,45 +7,45 @@
<meta name="keywords" content="how-to-contribute" />
<meta name="description" content="how-to-contribute" />
<!-- 网页标签标题 -->
- <title>How to Contribute - Apache InLong</title>
+ <title>How to Contribute - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
<div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! inlong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>
-<p>We use a review-then-commit workflow in InLong for all contributions.</p>
+<p>The Apache TubeMQ(incubating) community welcomes contributions from anyone with a passion for distributed systems! TubeMQ has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>
+<p>We use a review-then-commit workflow in TubeMQ for all contributions.</p>
<p><strong>For larger contributions or those that affect multiple components:</strong></p>
<ol>
-<li><strong>Engage</strong>: We encourage you to work with the InLong community on the <a href="https://jira.apache.org/jira/browse/inlong">JIRA</a> and <a href="../contact.html">developer’s mailing list</a> to identify good areas for contribution.</li>
+<li><strong>Engage</strong>: We encourage you to work with the TubeMQ community on the <a href="https://jira.apache.org/jira/browse/TUBEMQ">JIRA</a> and <a href="../contact.html">developer’s mailing list</a> to identify good areas for contribution.</li>
<li><strong>Design:</strong> More complicated contributions will likely benefit from some early discussion in order to scope and design them well.</li>
</ol>
<p><strong>For all contributions:</strong></p>
<ol>
<li><strong>Code:</strong> The you-know-what part.</li>
-<li><strong>Review:</strong> Submit a pull request with your contribution to our <a href="https://github.com/apache/incubator-inlong">GitHub Repo</a>. Work with a committer to review and iterate on the code, if needed.</li>
-<li><strong>Commit:</strong> Once at least 1 InLong committer has approved the pull request, a InLong committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).</li>
+<li><strong>Review:</strong> Submit a pull request with your contribution to our <a href="https://github.com/apache/incubator-tubemq">GitHub Repo</a>. Work with a committer to review and iterate on the code, if needed.</li>
+<li><strong>Commit:</strong> Once at least 1 TubeMQ committer has approved the pull request, a TubeMQ committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).</li>
</ol>
<p>We look forward to working with you!</p>
<h2>Engage</h2>
<h3>Mailing list(s)</h3>
-<p>We discuss design and implementation issues on the <a href="mailto:dev@inlong.apache.org">dev@inlong.apache.org</a> mailing list, which is archived <a href="https://lists.apache.org/list.html?dev@inlong.apache.org">here</a>. Join by emailing <a href="mailto:dev-subscribe@inlong.apache.org"><code>dev-subscribe@inlong.apache.org</code></a>.</p>
+<p>We discuss design and implementation issues on the <a href="mailto:dev@tubemq.apache.org">dev@tubemq.apache.org</a> mailing list, which is archived <a href="https://lists.apache.org/list.html?dev@tubemq.apache.org">here</a>. Join by emailing <a href="mailto:dev-subscribe@tubemq.apache.org"><code>dev-subscribe@tubemq.apache.org</code></a>.</p>
<h3>JIRA</h3>
-<p>We are using <a href="https://jira.apache.org/jira/browse/inlong">JIRA</a> as the issue tracking
-and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.</p>
+<p>We are using <a href="https://jira.apache.org/jira/browse/TUBEMQ">JIRA</a> as the issue tracking
+and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all TubeMQ related work are being tracked there.</p>
<p>If you do not already have an JIRA account, sign up <a href="https://jira.apache.org/jira/secure/Signup!default.jspa">here</a>.</p>
-<p>If a quick <a href="https://jira.apache.org/jira/projects/inlong/issues">search</a> doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.</p>
+<p>If a quick <a href="https://jira.apache.org/jira/projects/TUBEMQ/issues">search</a> doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.</p>
<p>If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.</p>
<p>For moderate or large contributions, you should not start coding or writing a design document unless there is a corresponding JIRA issue assigned to you for that work. Any change requires an associated JIRA issue.</p>
<h2>Design</h2>
-<p>To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the inlong community before you start coding.</p>
-<p>We are using "inlong Improvement Proposals" for managing major changes to inlong. The list of all proposals is maintained in the inlong wiki at <a href="https://cwiki.apache.org/confluence/display/inlong/inlong+Improvement+Proposals">this page</a>.</p>
+<p>To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the TubeMQ community before you start coding.</p>
+<p>We are using "TubeMQ Improvement Proposals" for managing major changes to TubeMQ. The list of all proposals is maintained in the TubeMQ wiki at <a href="https://cwiki.apache.org/confluence/display/TUBEMQ/TubeMQ+Improvement+Proposals">this page</a>.</p>
<h2>Commit (committers only)</h2>
<p>Once the code has been peer reviewed by a committer, the next step is for the committer to merge it into the Github repo.</p>
<p>Pull requests should not be merged before the review has approved from at least 1 committer.</p>
-<p>For more about merging pull request, please refer to <a href="https://cwiki.apache.org/confluence/display/inlong/Merging+Pull+Requests">this page</a></p>
+<p>For more about merging pull request, please refer to <a href="https://cwiki.apache.org/confluence/display/TUBEMQ/Merging+Pull+Requests">this page</a></p>
<h2>Website Contributor List</h2>
-<p>We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of inlong. Thanks again to the following participants.</p>
+<p>We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of TubeMQ. Thanks again to the following participants.</p>
<ul>
<li>deepEvolution</li>
<li>missy</li>
diff --git a/en-us/docs/development/how-to-contribute.json b/en-us/docs/development/how-to-contribute.json
index 091c2e5..c67931a 100644
--- a/en-us/docs/development/how-to-contribute.json
+++ b/en-us/docs/development/how-to-contribute.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-contribute.md",
- "__html": "<h1>How to Contribute</h1>\n<p>The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! inlong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>\n<p>We use a review-then-commit workflow in InLong for all contributions.</p>\n<p><strong>For larger contributions or those that affect multiple components:</strong [...]
+ "__html": "<h1>How to Contribute</h1>\n<p>The Apache TubeMQ(incubating) community welcomes contributions from anyone with a passion for distributed systems! TubeMQ has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.</p>\n<p>We use a review-then-commit workflow in TubeMQ for all contributions.</p>\n<p><strong>For larger contributions or those that affect multiple components:</strong [...]
"link": "/en-us/docs/development/how-to-contribute.html",
"meta": {
- "title": "How to Contribute - Apache InLong"
+ "title": "How to Contribute - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-contribute.md b/en-us/docs/development/how-to-contribute.md
index 4312ba6..559efd6 100644
--- a/en-us/docs/development/how-to-contribute.md
+++ b/en-us/docs/development/how-to-contribute.md
@@ -1,23 +1,23 @@
---
-title: How to Contribute - Apache InLong
+title: How to Contribute - Apache TubeMQ
---
# How to Contribute
-The Apache InLong(incubating) community welcomes contributions from anyone with a passion for distributed systems! inlong has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.
+The Apache TubeMQ(incubating) community welcomes contributions from anyone with a passion for distributed systems! TubeMQ has many different opportunities for contributions -- write new examples/tutorials, add new user-facing libraries or participate on the documentation effort.
-We use a review-then-commit workflow in InLong for all contributions.
+We use a review-then-commit workflow in TubeMQ for all contributions.
**For larger contributions or those that affect multiple components:**
-1. **Engage**: We encourage you to work with the InLong community on the [JIRA](https://jira.apache.org/jira/browse/inlong) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
+1. **Engage**: We encourage you to work with the TubeMQ community on the [JIRA](https://jira.apache.org/jira/browse/TUBEMQ) and [developer’s mailing list](../contact.html) to identify good areas for contribution.
2. **Design:** More complicated contributions will likely benefit from some early discussion in order to scope and design them well.
**For all contributions:**
1. **Code:** The you-know-what part.
-2. **Review:** Submit a pull request with your contribution to our [GitHub Repo](https://github.com/apache/incubator-inlong). Work with a committer to review and iterate on the code, if needed.
-3. **Commit:** Once at least 1 InLong committer has approved the pull request, a InLong committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).
+2. **Review:** Submit a pull request with your contribution to our [GitHub Repo](https://github.com/apache/incubator-tubemq). Work with a committer to review and iterate on the code, if needed.
+3. **Commit:** Once at least 1 TubeMQ committer has approved the pull request, a TubeMQ committer will merge it into the master branch (and potentially backport to stable branches in case of bug fixes).
We look forward to working with you!
@@ -25,16 +25,16 @@ We look forward to working with you!
### Mailing list(s)
-We discuss design and implementation issues on the [dev@inlong.apache.org](mailto:dev@inlong.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@inlong.apache.org). Join by emailing [`dev-subscribe@inlong.apache.org`](mailto:dev-subscribe@inlong.apache.org).
+We discuss design and implementation issues on the [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) mailing list, which is archived [here](https://lists.apache.org/list.html?dev@tubemq.apache.org). Join by emailing [`dev-subscribe@tubemq.apache.org`](mailto:dev-subscribe@tubemq.apache.org).
### JIRA
-We are using [JIRA](https://jira.apache.org/jira/browse/inlong) as the issue tracking
-and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all InLong related work are being tracked there.
+We are using [JIRA](https://jira.apache.org/jira/browse/TUBEMQ) as the issue tracking
+and project management tool, as well as a way to communicate among a very diverse and distributed set of contributors. To be able to gather feedback, avoid frustration, and avoid duplicated efforts all TubeMQ related work are being tracked there.
If you do not already have an JIRA account, sign up [here](https://jira.apache.org/jira/secure/Signup!default.jspa).
-If a quick [search](https://jira.apache.org/jira/projects/inlong/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
+If a quick [search](https://jira.apache.org/jira/projects/TUBEMQ/issues) doesn’t turn up an existing JIRA issue for the work you want to contribute, create it. Please discuss your idea with a committer in JIRA or, alternatively, on the developer mailing list.
If there’s an existing JIRA issue for your intended contribution, please comment about your intended work. Once the work is understood, a committer will assign the issue to you. If an issue is currently assigned, please check with the current assignee before reassigning.
@@ -42,9 +42,9 @@ For moderate or large contributions, you should not start coding or writing a de
## Design
-To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the inlong community before you start coding.
+To avoid potential frustration during the code review cycle, we encourage you to clearly scope and design non-trivial contributions with the TubeMQ community before you start coding.
-We are using "inlong Improvement Proposals" for managing major changes to inlong. The list of all proposals is maintained in the inlong wiki at [this page](https://cwiki.apache.org/confluence/display/inlong/inlong+Improvement+Proposals).
+We are using "TubeMQ Improvement Proposals" for managing major changes to TubeMQ. The list of all proposals is maintained in the TubeMQ wiki at [this page](https://cwiki.apache.org/confluence/display/TUBEMQ/TubeMQ+Improvement+Proposals).
## Commit (committers only)
@@ -52,10 +52,10 @@ Once the code has been peer reviewed by a committer, the next step is for the co
Pull requests should not be merged before the review has approved from at least 1 committer.
-For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/inlong/Merging+Pull+Requests)
+For more about merging pull request, please refer to [this page](https://cwiki.apache.org/confluence/display/TUBEMQ/Merging+Pull+Requests)
## Website Contributor List
-We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of inlong. Thanks again to the following participants.
+We are very pleased to announce some contributors here. They have made a lot of contributions in the translation of TubeMQ. Thanks again to the following participants.
- deepEvolution
- missy
- min.yang
diff --git a/en-us/docs/development/how-to-release.html b/en-us/docs/development/how-to-release.html
index 56cf2c1..efdd52c 100644
--- a/en-us/docs/development/how-to-release.html
+++ b/en-us/docs/development/how-to-release.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="how-to-release" />
<meta name="description" content="how-to-release" />
<!-- 网页标签标题 -->
- <title>How to Release - Apache inlong</title>
+ <title>How to Release - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -19,7 +19,7 @@
</blockquote>
<h2>0. 前言</h2>
<p>Source Release是Apache关注的重点，也是发布的必须内容；
-Binary Release是可选项，inlong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>
+Binary Release是可选项，TubeMQ可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>
<p>请参考以下链接，找到更多关于ASF的发布指南:</p>
<p><a href="https://incubator.apache.org/guides/releasemanagement.html">Apache Release Guide</a></p>
<p><a href="https://incubator.apache.org/">Apache incubator 官网</a></p>
@@ -122,22 +122,22 @@ sub rsa4096 2020-05-18 [E]
<blockquote>
<p>这个步骤需要使用SVN</p>
</blockquote>
-<p>DEV分支的svn库是 <a href="https://dist.apache.org/repos/dist/dev/incubator/inlong">https://dist.apache.org/repos/dist/dev/incubator/inlong</a></p>
-<p>Release分支的SVN库是 <a href="https://dist.apache.org/repos/dist/release/incubator/inlong">https://dist.apache.org/repos/dist/release/incubator/inlong</a></p>
+<p>DEV分支的svn库是 <a href="https://dist.apache.org/repos/dist/dev/incubator/tubemq">https://dist.apache.org/repos/dist/dev/incubator/tubemq</a></p>
+<p>Release分支的SVN库是 <a href="https://dist.apache.org/repos/dist/release/incubator/tubemq">https://dist.apache.org/repos/dist/release/incubator/tubemq</a></p>
<h4>1.5.1 在dev分支中添加公钥到KEYS，用于发布RC版本</h4>
-<pre><code class="language-shell">➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+<pre><code class="language-shell">➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
<span class="hljs-meta">#</span><span class="bash"> 这个步骤比较慢，会把所有版本都拷贝下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传</span>
-➜ ~ cd inlong-dist-dev
-➜ inlong-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ cd tubemq-dist-dev
+➜ tubemq-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
</code></pre>
<h4>1.5.2 在release分支中添加公钥到KEYS，用于发布正式版本</h4>
-<pre><code class="language-shell">➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/inlong /tmp/inlong-dist-release
-➜ ~ cd inlong-dist-release
-➜ inlong-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+<pre><code class="language-shell">➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/tubemq /tmp/tubemq-dist-release
+➜ ~ cd tubemq-dist-release
+➜ tubemq-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
</code></pre>
<h3>1.6 上传GPG公钥到Github账户</h3>
<ol>
@@ -210,19 +210,19 @@ sub rsa4096 2020-05-18 [E]
<blockquote>
<p>tag创建成功后，我需要将tag源码打包成一个tar包</p>
</blockquote>
-<pre><code class="language-shell">mkdir /tmp/apache-inlong-${release_version}-${rc_version}
-git archive --format=tar.gz --output="/tmp/apache-inlong-${release_version}-${rc_version}/apache-inlong-${release_version}-src.tar.gz" --prefix="apache-inlong-${release_version}/" $git_tag
+<pre><code class="language-shell">mkdir /tmp/apache-tubemq-${release_version}-${rc_version}
+git archive --format=tar.gz --output="/tmp/apache-tubemq-${release_version}-${rc_version}/apache-tubemq-${release_version}-src.tar.gz" --prefix="apache-tubemq-${release_version}/" $git_tag
</code></pre>
<h3>3.4 打包二进制包</h3>
<blockquote>
<p>编译上一步打包的源码</p>
</blockquote>
-<pre><code class="language-shell">cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version} # 进入源码目录
+<pre><code class="language-shell">cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version} # 进入源码目录
mvn compile clean install package -DskipTests # 编译
-cp ./inlong-client/target/apache-inlong-client-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
-cp ./inlong-server/target/apache-inlong-server-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-client/target/apache-tubemq-client-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-server/target/apache-tubemq-server-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
</code></pre>
<h3>3.5 对源码包/二进制包进行签名/sha512</h3>
<pre><code class="language-shell">for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i > $i.sha512 ; done # 计算SHA512
@@ -235,9 +235,9 @@ for i in *.tar.gz; do echo $i; gpg --armor --output $i.asc --detach-sig $i ; don
</code></pre>
<h2>4. 准备Apache发布</h2>
<h3>4.1 发布jar包到Apache Nexus仓库</h3>
-<pre><code class="language-shell">cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version}
+<pre><code class="language-shell">cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version}
mvn -DskipTests deploy -Papache-release -Dmaven.javadoc.skip=true # 开始上传
</code></pre>
<h3>4.2 上传tag到git仓库</h3>
@@ -245,17 +245,17 @@ mvn -DskipTests deploy -Papache-release -Dmaven.javadoc.skip=true # 开始上
</code></pre>
<h3>4.3 上传编译好的文件到dist</h3>
<blockquote>
-<p>这个步骤需要使用SVN, DEV分支的svn库是 <a href="https://dist.apache.org/repos/dist/dev/incubator/inlong">https://dist.apache.org/repos/dist/dev/incubator/inlong</a></p>
+<p>这个步骤需要使用SVN, DEV分支的svn库是 <a href="https://dist.apache.org/repos/dist/dev/incubator/tubemq">https://dist.apache.org/repos/dist/dev/incubator/tubemq</a></p>
</blockquote>
-<h3>4.3.1 将inlong checkout到本地目录</h3>
+<h3>4.3.1 将TubeMQ checkout到本地目录</h3>
<pre><code class="language-shell"><span class="hljs-meta">#</span><span class="bash"> 这个步骤可能会比较慢，会把所有版本都考下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传</span>
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
</code></pre>
<h3>4.3.2 添加public key到KEYS文件并提交到SVN仓库</h3>
-<pre><code class="language-shell">cd /tmp/inlong-dist-dev
+<pre><code class="language-shell">cd /tmp/tubemq-dist-dev
mkdir ${release_version}-${rc_version} #创建版本目录
<span class="hljs-meta">#</span><span class="bash"> 将源码包和签名包拷贝到此处</span>
-cp /tmp/apache-inlong-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
+cp /tmp/apache-tubemq-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
svn status # 检查svn状态
svn add ${release_version}-${rc_version} # 添加到svn版本
svn status # 检查svn状态
@@ -268,61 +268,61 @@ svn commit -m 'prepare for ${release_version} ${rc_version}'# 提交至svn远程
<ol>
<li><strong>先登录</strong><a href="http://repository.apache.org">http://repository.apache.org</a> , 使用Apache账号登录</li>
<li>点击左侧的Staging repositories，</li>
-<li>搜索inlong关键字，选择你最近上传的仓库</li>
+<li>搜索TubeMQ关键字，选择你最近上传的仓库</li>
<li>点击上方的Close按钮，这个过程会进行一系列检查</li>
<li>检查通过以后, 在下方的Summary标签页上出现一个连接，请保存好这个链接，需要放在接下来的投票邮件当中。
-链接应该是类似这样的: <code>https://repository.apache.org/content/repositories/orgapacheinlong-xxxx</code></li>
+链接应该是类似这样的: <code>https://repository.apache.org/content/repositories/orgapachetubemq-xxxx</code></li>
</ol>
<p>WARN: 请注意点击Close可能会出现失败，请检查失败原因并处理</p>
<h2>5. 进入投票</h2>
<blockquote>
-<p>inlong仍旧在孵化中，需要进行两次投票，</p>
+<p>TubeMQ仍旧在孵化中，需要进行两次投票，</p>
</blockquote>
<ul>
-<li>inlong社区投票，发邮件至：<code>dev@inlong.apache.org</code></li>
+<li>TubeMQ社区投票，发邮件至：<code>dev@tubemq.apache.org</code></li>
<li>incubator社区投票，发邮件至：<code>general@incubator.apache.org</code>
-inlong毕业之后，只需要在inlong社区投票</li>
+TubeMQ毕业之后，只需要在TubeMQ社区投票</li>
</ul>
-<h3>5.1 inlong社区投票</h3>
+<h3>5.1 TubeMQ社区投票</h3>
<h4>5.1.1 投票模板</h4>
-<pre><code class="language-html">标题：[VOTE] Release Apache inlong ${release_version} ${rc_version}
+<pre><code class="language-html">标题：[VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
- This is a call for vote to release Apache inlong version ${release_version}-${rc_version}.
+ This is a call for vote to release Apache TubeMQ version ${release_version}-${rc_version}.
The tag to be voted on is ${release_version}-${rc_version}:
- https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
The release tarball, signature, and checksums can be found at:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Maven artifacts are available in a staging repository at:
- https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}
+ https://repository.apache.org/content/repositories/orgapachetubemq-{staging-id}
Artifacts were signed with the {YOUR_PUB_KEY} key which can be found in:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
${release_version} includes ~ ${issue_count} bug and improvement fixes done since last versions which can be found at:
- https://github.com/apache/incubator-inlong/blob/${release_version}-${rc_version}/CHANGES.md
+ https://github.com/apache/incubator-tubemq/blob/${release_version}-${rc_version}/CHANGES.md
Please download, verify, and test.
The VOTE will remain open for at least 72 hours.
- [ ] +1 Release this package as Apache inlong ${release_version}
+ [ ] +1 Release this package as Apache TubeMQ ${release_version}
[ ] +0
[ ] -1 Do not release this package because...
- To learn more about apache inlong, please see
- http://inlong.apache.org/
+ To learn more about apache tubemq, please see
+ http://tubemq.apache.org/
Checklist for reference:
@@ -338,14 +338,14 @@ Hello Apache inlong PPMC and Community,
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Thanks,
-Your inlong Release Manager
+Your TubeMQ Release Manager
</code></pre>
<h4>5.1.2 宣布投票结果模板</h4>
-<pre><code class="language-html">标题：[RESULT][VOTE] Release Apache inlong ${release_version} ${rc_version}
+<pre><code class="language-html">标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
xx (+1 non-binding) votes from the PPMC,
@@ -359,42 +359,42 @@ Hello Apache inlong PPMC and Community,
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
-Your inlong Release Manager
+Your TubeMQ Release Manager
</code></pre>
<h3>5.2 incubator社区投票</h3>
<h4>5.2.1 投票模板</h4>
-<pre><code class="language-html">标题：[VOTE] Release Apache inlong (Incubating) ${release_version} ${rc_version}
+<pre><code class="language-html">标题：[VOTE] Release Apache TubeMQ (Incubating) ${release_version} ${rc_version}
内容：
Hello Incubator Community,
- This is a call for a vote to release Apache inlong (Incubating) version
+ This is a call for a vote to release Apache TubeMQ (Incubating) version
${release_version} ${rc_version}
- The Apache inlong community has voted on and approved a proposal to release
- Apache inlong (Incubating) version ${release_version} ${rc_version}
+ The Apache TubeMQ community has voted on and approved a proposal to release
+ Apache TubeMQ (Incubating) version ${release_version} ${rc_version}
We now kindly request the Incubator PMC members review and vote on this
incubator release.
- inlong community vote thread:
+ TubeMQ community vote thread:
• [投票链接]
Vote result thread:
• [投票结果链接]
The release candidate:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Git tag for the release:
- • https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
Release notes:
- • https://github.com/apache/incubator-inlong/releases/tag/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/releases/tag/${release_version}-${rc_version}
The artifacts signed with PGP key [填写你个人的KEY], corresponding to [填写你个人的邮箱], that can be found in keys file:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
The vote will be open for at least 72 hours or until necessary number of votes are reached.
@@ -405,16 +405,16 @@ Hello Incubator Community,
[ ] -1 disapprove with the reason
Thanks,
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
</code></pre>
<h4>5.2.2 宣布投票结果模板</h4>
-<pre><code class="language-html">标题：[RESULT][VOTE] Release Apache inlong ${release_version} {rc_version}
+<pre><code class="language-html">标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} {rc_version}
内容：
Hi all
-Thanks for reviewing and voting for Apache inlong (Incubating) ${release_version} {rc_version}
+Thanks for reviewing and voting for Apache TubeMQ (Incubating) ${release_version} {rc_version}
release, I am happy to announce the release voting has passed with [投票结果数]
binding votes, no +0 or -1 votes. Binding votes are from IPMC
@@ -426,23 +426,23 @@ The voting thread is:
[投票链接]
Many thanks for all our mentors helping us with the release procedure, and
-all IPMC helped us to review and vote for Apache inlong (Incubating) release. I will
+all IPMC helped us to review and vote for Apache TubeMQ (Incubating) release. I will
be working on publishing the artifacts soon.
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
</code></pre>
<h2>6. 正式发布</h2>
<h3>6.1 合并release-${release_version}分支的改动到master分支</h3>
<h3>6.2 将源码和二进制包从svn的dev目录移动到release目录</h3>
-<pre><code class="language-shell">svn mv https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/inlong/${release_version} -m "Release ${release_version}"
+<pre><code class="language-shell">svn mv https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/tubemq/${release_version} -m "Release ${release_version}"
</code></pre>
<h3>6.3 确认dev和release下的包是否正确</h3>
<ol>
-<li>确认<a href="https://dist.apache.org/repos/dist/dev/incubator/inlong/">dev</a>下的<code>${release_version}-${rc_version}</code>已被删除</li>
-<li>删除<a href="https://dist.apache.org/repos/dist/release/incubator/inlong/">release</a>目录下上一个版本的发布包，这些包会被自动保存在<a href="https://archive.apache.org/dist/incubator/inlong/">这里</a></li>
+<li>确认<a href="https://dist.apache.org/repos/dist/dev/incubator/tubemq/">dev</a>下的<code>${release_version}-${rc_version}</code>已被删除</li>
+<li>删除<a href="https://dist.apache.org/repos/dist/release/incubator/tubemq/">release</a>目录下上一个版本的发布包，这些包会被自动保存在<a href="https://archive.apache.org/dist/incubator/tubemq/">这里</a></li>
</ol>
-<pre><code class="language-shell">svn delete https://dist.apache.org/repos/dist/release/incubator/inlong/${last_release_version} -m "Delete ${last_release_version}"
+<pre><code class="language-shell">svn delete https://dist.apache.org/repos/dist/release/incubator/tubemq/${last_release_version} -m "Delete ${last_release_version}"
</code></pre>
<h3>6.4 在Apache Staging仓库发布版本</h3>
<blockquote>
@@ -451,36 +451,36 @@ On behalf of Apache inlong (Incubating) community
<ol>
<li>登录http://repository.apache.org , 使用Apache账号登录</li>
<li>点击左侧的Staging repositories，</li>
-<li>搜索inlong关键字，选择你最近上传的仓库，投票邮件中指定的仓库</li>
+<li>搜索TubeMQ关键字，选择你最近上传的仓库，投票邮件中指定的仓库</li>
<li>点击上方的<code>Release</code>按钮，这个过程会进行一系列检查</li>
</ol>
<p><strong>等仓库同步到其他数据源，一般需要24小时</strong></p>
<h3>6.5 更新官网链接</h3>
-<h3>6.6. 发邮件到 <code>dev@inlong.apache.org</code> 和 <code>general@incubator.apache.org</code></h3>
+<h3>6.6. 发邮件到 <code>dev@tubemq.apache.org</code> 和 <code>general@incubator.apache.org</code></h3>
<p><strong>请确保6.4中的仓库已发布成功，一般是在6.4后的24小时后发布邮件</strong></p>
<p>宣布release邮件模板：</p>
-<pre><code class="language-html">标题： [ANNOUNCE] Release Apache inlong(incubating) ${release_version}
+<pre><code class="language-html">标题： [ANNOUNCE] Release Apache TubeMQ(incubating) ${release_version}
内容：
Hi all,
-The Apache inlong(incubating) community is pleased to announce
-that Apache inlong (incubating) ${release_version} has been released!
+The Apache TubeMQ(incubating) community is pleased to announce
+that Apache TubeMQ (incubating) ${release_version} has been released!
-Apache inlong is a trillion-records-scale distributed messaging queue (MQ) system,
+Apache TubeMQ is a trillion-records-scale distributed messaging queue (MQ) system,
focuses on data transmission and storage under massive data.
Download Links: xxx
Release Notes: xxx
-Website: https://inlong.apache.org/
+Website: https://tubemq.apache.org/
-inlong Resources:
-- Issue: https://issues.apache.org/jira/projects/inlong/issues
-- Mailing list: dev@inlong.apache.org
+TubeMQ Resources:
+- Issue: https://issues.apache.org/jira/projects/TUBEMQ/issues
+- Mailing list: dev@tubemq.apache.org
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
</code></pre>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
diff --git a/en-us/docs/development/how-to-release.json b/en-us/docs/development/how-to-release.json
index d362bcd..0440910 100644
--- a/en-us/docs/development/how-to-release.json
+++ b/en-us/docs/development/how-to-release.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-release.md",
- "__html": "<h1>如何发布版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<h2>0. 前言</h2>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，inlong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release [...]
+ "__html": "<h1>如何发布版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<blockquote>\n<p>本文主要介绍了Release Manager如何按照Apache的流程发布版本，</p>\n</blockquote>\n<h2>0. 前言</h2>\n<p>Source Release是Apache关注的重点，也是发布的必须内容；\nBinary Release是可选项，TubeMQ可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。</p>\n<p>请参考以下链接，找到更多关于ASF的发布指南:</p>\n<p><a href=\"https://incubator.apache.org/guides/releasemanagement.html\">Apache Release [...]
"link": "/en-us/docs/development/how-to-release.html",
"meta": {
- "title": "How to Release - Apache inlong"
+ "title": "How to Release - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-release.md b/en-us/docs/development/how-to-release.md
index 58026cc..a1b7a70 100644
--- a/en-us/docs/development/how-to-release.md
+++ b/en-us/docs/development/how-to-release.md
@@ -1,5 +1,5 @@
---
-title: How to Release - Apache inlong
+title: How to Release - Apache TubeMQ
---
# 如何发布版本
@@ -10,7 +10,7 @@ title: How to Release - Apache inlong
## 0. 前言
Source Release是Apache关注的重点，也是发布的必须内容；
-Binary Release是可选项，inlong可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
+Binary Release是可选项，TubeMQ可以选择是否发布二进制包到Apache仓库或者发布到Maven中央仓库。
请参考以下链接，找到更多关于ASF的发布指南:
@@ -125,29 +125,29 @@ http://keys.gnupg.net
> 这个步骤需要使用SVN
-DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/inlong
+Release分支的SVN库是 https://dist.apache.org/repos/dist/release/incubator/tubemq
#### 1.5.1 在dev分支中添加公钥到KEYS，用于发布RC版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+➜ ~ svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
# 这个步骤比较慢，会把所有版本都拷贝下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-➜ ~ cd inlong-dist-dev
-➜ inlong-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ cd tubemq-dist-dev
+➜ tubemq-dist-dev ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-dev ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-dev ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
#### 1.5.2 在release分支中添加公钥到KEYS，用于发布正式版本
```shell
-➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/inlong /tmp/inlong-dist-release
-➜ ~ cd inlong-dist-release
-➜ inlong-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
-➜ inlong-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
-➜ inlong-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
+➜ ~ svn co https://dist.apache.org/repos/dist/release/incubator/tubemq /tmp/tubemq-dist-release
+➜ ~ cd tubemq-dist-release
+➜ tubemq-dist-release ~ (gpg --list-sigs YOUR_NAME@apache.org && gpg --export --armor YOUR_NAME@apache.org) >> KEYS # 追加你生成的KEY到文件KEYS中, 追加后最好检查一下是否正确
+➜ tubemq-dist-release ~ svn add . # 如果之前存在KEYS文件，则不需要
+➜ tubemq-dist-release ~ svn ci -m "add gpg key for YOUR_NAME" # 接下来会要求输入用户名和密码，就用你的apache的用户名和密码。
```
### 1.6 上传GPG公钥到Github账户
@@ -222,20 +222,20 @@ $ git config user.signingkey ${KEY_ID}
> tag创建成功后，我需要将tag源码打包成一个tar包
```shell
-mkdir /tmp/apache-inlong-${release_version}-${rc_version}
-git archive --format=tar.gz --output="/tmp/apache-inlong-${release_version}-${rc_version}/apache-inlong-${release_version}-src.tar.gz" --prefix="apache-inlong-${release_version}/" $git_tag
+mkdir /tmp/apache-tubemq-${release_version}-${rc_version}
+git archive --format=tar.gz --output="/tmp/apache-tubemq-${release_version}-${rc_version}/apache-tubemq-${release_version}-src.tar.gz" --prefix="apache-tubemq-${release_version}/" $git_tag
```
### 3.4 打包二进制包
> 编译上一步打包的源码
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version} # 进入源码目录
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version} # 进入源码目录
mvn compile clean install package -DskipTests # 编译
-cp ./inlong-client/target/apache-inlong-client-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
-cp ./inlong-server/target/apache-inlong-server-${release_version}-bin.tar.gz /tmp/apache-inlong-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-client/target/apache-tubemq-client-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝client包到源码包目录下，方面下一步对包进行签名
+cp ./tubemq-server/target/apache-tubemq-server-${release_version}-bin.tar.gz /tmp/apache-tubemq-${release_version}-${rc_version}/ # 拷贝server包到源码包目录下，方面下一步对包进行签名
```
### 3.5 对源码包/二进制包进行签名/sha512
@@ -253,9 +253,9 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
## 4. 准备Apache发布
### 4.1 发布jar包到Apache Nexus仓库
```shell
-cd /tmp/apache-inlong-${release_version}-${rc_version} # 进入源码包目录
-tar xzvf apache-inlong-${release_version}-src.tar.gz #解压源码包
-cd apache-inlong-${release_version}
+cd /tmp/apache-tubemq-${release_version}-${rc_version} # 进入源码包目录
+tar xzvf apache-tubemq-${release_version}-src.tar.gz #解压源码包
+cd apache-tubemq-${release_version}
mvn -DskipTests deploy -Papache-release -Dmaven.javadoc.skip=true # 开始上传
```
@@ -266,20 +266,20 @@ git push origin ${release_version}-${rc_version}
```
### 4.3 上传编译好的文件到dist
-> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/inlong
+> 这个步骤需要使用SVN, DEV分支的svn库是 https://dist.apache.org/repos/dist/dev/incubator/tubemq
-### 4.3.1 将inlong checkout到本地目录
+### 4.3.1 将TubeMQ checkout到本地目录
```shell
# 这个步骤可能会比较慢，会把所有版本都考下来，如果网断了，用svn cleanup删掉锁，重新执行一下，会断点续传
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong /tmp/inlong-dist-dev
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq /tmp/tubemq-dist-dev
```
### 4.3.2 添加public key到KEYS文件并提交到SVN仓库
```shell
-cd /tmp/inlong-dist-dev
+cd /tmp/tubemq-dist-dev
mkdir ${release_version}-${rc_version} #创建版本目录
# 将源码包和签名包拷贝到此处
-cp /tmp/apache-inlong-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
+cp /tmp/apache-tubemq-${release_version}-${rc_version}/*tar.gz* ${release_version}-${rc_version}/
svn status # 检查svn状态
svn add ${release_version}-${rc_version} # 添加到svn版本
svn status # 检查svn状态
@@ -289,62 +289,62 @@ svn commit -m 'prepare for ${release_version} ${rc_version}'# 提交至svn远程
> 请确保所有的artifact都是ok的
1. **先登录**http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库
4. 点击上方的Close按钮，这个过程会进行一系列检查
5. 检查通过以后, 在下方的Summary标签页上出现一个连接，请保存好这个链接，需要放在接下来的投票邮件当中。
-链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapacheinlong-xxxx`
+链接应该是类似这样的: `https://repository.apache.org/content/repositories/orgapachetubemq-xxxx`
WARN: 请注意点击Close可能会出现失败，请检查失败原因并处理
## 5. 进入投票
-> inlong仍旧在孵化中，需要进行两次投票，
-- inlong社区投票，发邮件至：`dev@inlong.apache.org`
+> TubeMQ仍旧在孵化中，需要进行两次投票，
+- TubeMQ社区投票，发邮件至：`dev@tubemq.apache.org`
- incubator社区投票，发邮件至：`general@incubator.apache.org`
-inlong毕业之后，只需要在inlong社区投票
+TubeMQ毕业之后，只需要在TubeMQ社区投票
-### 5.1 inlong社区投票
+### 5.1 TubeMQ社区投票
#### 5.1.1 投票模板
```html
-标题：[VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
- This is a call for vote to release Apache inlong version ${release_version}-${rc_version}.
+ This is a call for vote to release Apache TubeMQ version ${release_version}-${rc_version}.
The tag to be voted on is ${release_version}-${rc_version}:
- https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
The release tarball, signature, and checksums can be found at:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Maven artifacts are available in a staging repository at:
- https://repository.apache.org/content/repositories/orgapacheinlong-{staging-id}
+ https://repository.apache.org/content/repositories/orgapachetubemq-{staging-id}
Artifacts were signed with the {YOUR_PUB_KEY} key which can be found in:
- https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
${release_version} includes ~ ${issue_count} bug and improvement fixes done since last versions which can be found at:
- https://github.com/apache/incubator-inlong/blob/${release_version}-${rc_version}/CHANGES.md
+ https://github.com/apache/incubator-tubemq/blob/${release_version}-${rc_version}/CHANGES.md
Please download, verify, and test.
The VOTE will remain open for at least 72 hours.
- [ ] +1 Release this package as Apache inlong ${release_version}
+ [ ] +1 Release this package as Apache TubeMQ ${release_version}
[ ] +0
[ ] -1 Do not release this package because...
- To learn more about apache inlong, please see
- http://inlong.apache.org/
+ To learn more about apache tubemq, please see
+ http://tubemq.apache.org/
Checklist for reference:
@@ -360,16 +360,16 @@ Hello Apache inlong PPMC and Community,
https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist
Thanks,
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
#### 5.1.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} ${rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} ${rc_version}
内容：
-Hello Apache inlong PPMC and Community,
+Hello Apache TubeMQ PPMC and Community,
The vote closes now as 72hr have passed. The vote PASSES with
xx (+1 non-binding) votes from the PPMC,
@@ -383,7 +383,7 @@ Hello Apache inlong PPMC and Community,
If this vote passes also, the release is accepted and will be published.
Thank you for your support.
-Your inlong Release Manager
+Your TubeMQ Release Manager
```
### 5.2 incubator社区投票
@@ -391,38 +391,38 @@ Your inlong Release Manager
#### 5.2.1 投票模板
```html
-标题：[VOTE] Release Apache inlong (Incubating) ${release_version} ${rc_version}
+标题：[VOTE] Release Apache TubeMQ (Incubating) ${release_version} ${rc_version}
内容：
Hello Incubator Community,
- This is a call for a vote to release Apache inlong (Incubating) version
+ This is a call for a vote to release Apache TubeMQ (Incubating) version
${release_version} ${rc_version}
- The Apache inlong community has voted on and approved a proposal to release
- Apache inlong (Incubating) version ${release_version} ${rc_version}
+ The Apache TubeMQ community has voted on and approved a proposal to release
+ Apache TubeMQ (Incubating) version ${release_version} ${rc_version}
We now kindly request the Incubator PMC members review and vote on this
incubator release.
- inlong community vote thread:
+ TubeMQ community vote thread:
• [投票链接]
Vote result thread:
• [投票结果链接]
The release candidate:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
Git tag for the release:
- • https://github.com/apache/incubator-inlong/tree/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/tree/${release_version}-${rc_version}
Release notes:
- • https://github.com/apache/incubator-inlong/releases/tag/${release_version}-${rc_version}
+ • https://github.com/apache/incubator-tubemq/releases/tag/${release_version}-${rc_version}
The artifacts signed with PGP key [填写你个人的KEY], corresponding to [填写你个人的邮箱], that can be found in keys file:
- • https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS
+ • https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS
The vote will be open for at least 72 hours or until necessary number of votes are reached.
@@ -433,18 +433,18 @@ Hello Incubator Community,
[ ] -1 disapprove with the reason
Thanks,
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
#### 5.2.2 宣布投票结果模板
```html
-标题：[RESULT][VOTE] Release Apache inlong ${release_version} {rc_version}
+标题：[RESULT][VOTE] Release Apache TubeMQ ${release_version} {rc_version}
内容：
Hi all
-Thanks for reviewing and voting for Apache inlong (Incubating) ${release_version} {rc_version}
+Thanks for reviewing and voting for Apache TubeMQ (Incubating) ${release_version} {rc_version}
release, I am happy to announce the release voting has passed with [投票结果数]
binding votes, no +0 or -1 votes. Binding votes are from IPMC
@@ -456,11 +456,11 @@ The voting thread is:
[投票链接]
Many thanks for all our mentors helping us with the release procedure, and
-all IPMC helped us to review and vote for Apache inlong (Incubating) release. I will
+all IPMC helped us to review and vote for Apache TubeMQ (Incubating) release. I will
be working on publishing the artifacts soon.
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
## 6. 正式发布
@@ -468,51 +468,51 @@ On behalf of Apache inlong (Incubating) community
### 6.1 合并release-${release_version}分支的改动到master分支
### 6.2 将源码和二进制包从svn的dev目录移动到release目录
```shell
-svn mv https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/inlong/${release_version} -m "Release ${release_version}"
+svn mv https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version} https://dist.apache.org/repos/dist/release/incubator/tubemq/${release_version} -m "Release ${release_version}"
```
### 6.3 确认dev和release下的包是否正确
-1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/inlong/)下的`${release_version}-${rc_version}`已被删除
-2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/inlong/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/inlong/)
+1. 确认[dev](https://dist.apache.org/repos/dist/dev/incubator/tubemq/)下的`${release_version}-${rc_version}`已被删除
+2. 删除[release](https://dist.apache.org/repos/dist/release/incubator/tubemq/)目录下上一个版本的发布包，这些包会被自动保存在[这里](https://archive.apache.org/dist/incubator/tubemq/)
```shell
-svn delete https://dist.apache.org/repos/dist/release/incubator/inlong/${last_release_version} -m "Delete ${last_release_version}"
+svn delete https://dist.apache.org/repos/dist/release/incubator/tubemq/${last_release_version} -m "Delete ${last_release_version}"
```
### 6.4 在Apache Staging仓库发布版本
> 请确保所有的artifact都是ok的
1. 登录http://repository.apache.org , 使用Apache账号登录
2. 点击左侧的Staging repositories，
-3. 搜索inlong关键字，选择你最近上传的仓库，投票邮件中指定的仓库
+3. 搜索TubeMQ关键字，选择你最近上传的仓库，投票邮件中指定的仓库
4. 点击上方的`Release`按钮，这个过程会进行一系列检查
**等仓库同步到其他数据源，一般需要24小时**
### 6.5 更新官网链接
-### 6.6. 发邮件到 `dev@inlong.apache.org` 和 `general@incubator.apache.org`
+### 6.6. 发邮件到 `dev@tubemq.apache.org` 和 `general@incubator.apache.org`
**请确保6.4中的仓库已发布成功，一般是在6.4后的24小时后发布邮件**
宣布release邮件模板：
```html
-标题： [ANNOUNCE] Release Apache inlong(incubating) ${release_version}
+标题： [ANNOUNCE] Release Apache TubeMQ(incubating) ${release_version}
内容：
Hi all,
-The Apache inlong(incubating) community is pleased to announce
-that Apache inlong (incubating) ${release_version} has been released!
+The Apache TubeMQ(incubating) community is pleased to announce
+that Apache TubeMQ (incubating) ${release_version} has been released!
-Apache inlong is a trillion-records-scale distributed messaging queue (MQ) system,
+Apache TubeMQ is a trillion-records-scale distributed messaging queue (MQ) system,
focuses on data transmission and storage under massive data.
Download Links: xxx
Release Notes: xxx
-Website: https://inlong.apache.org/
+Website: https://tubemq.apache.org/
-inlong Resources:
-- Issue: https://issues.apache.org/jira/projects/inlong/issues
-- Mailing list: dev@inlong.apache.org
+TubeMQ Resources:
+- Issue: https://issues.apache.org/jira/projects/TUBEMQ/issues
+- Mailing list: dev@tubemq.apache.org
Thanks
-On behalf of Apache inlong (Incubating) community
+On behalf of Apache TubeMQ (Incubating) community
```
diff --git a/en-us/docs/development/how-to-subscribe.html b/en-us/docs/development/how-to-subscribe.html
index dad3126..567b931 100644
--- a/en-us/docs/development/how-to-subscribe.html
+++ b/en-us/docs/development/how-to-subscribe.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="how-to-subscribe" />
<meta name="description" content="how-to-subscribe" />
<!-- 网页标签标题 -->
- <title>Subscribe Mailing list - Apache inlong</title>
+ <title>Subscribe Mailing list - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -16,8 +16,8 @@
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<h2>1. 前言</h2>
<p>邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
-订阅邮件后，你可以第一时间获取inlong社区的动态，可以与社区保持同步。</p>
-<h4>inlong项目邮件列表</h4>
+订阅邮件后，你可以第一时间获取TubeMQ社区的动态，可以与社区保持同步。</p>
+<h4>TubeMQ项目邮件列表</h4>
<table>
<thead>
<tr>
@@ -30,38 +30,38 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="mailto:dev@inlong.apache.org">dev@inlong.apache.org</a></td>
+<td style="text-align:left"><a href="mailto:dev@tubemq.apache.org">dev@tubemq.apache.org</a></td>
<td style="text-align:left">社区活动信息</td>
-<td style="text-align:left"><a href="mailto:dev-subscribe@inlong.apache.org">订阅</a></td>
-<td style="text-align:left"><a href="mailto:dev-unsubscribe@inlong.apache.org">退订</a></td>
-<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/inlong-dev">归档</a></td>
+<td style="text-align:left"><a href="mailto:dev-subscribe@tubemq.apache.org">订阅</a></td>
+<td style="text-align:left"><a href="mailto:dev-unsubscribe@tubemq.apache.org">退订</a></td>
+<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/tubemq-dev">归档</a></td>
</tr>
<tr>
-<td style="text-align:left"><a href="mailto:commits@inlong.apache.org">commits@inlong.apache.org</a></td>
+<td style="text-align:left"><a href="mailto:commits@tubemq.apache.org">commits@tubemq.apache.org</a></td>
<td style="text-align:left">代码库更新信息</td>
-<td style="text-align:left"><a href="mailto:commits-subscribe@inlong.apache.org">订阅</a></td>
-<td style="text-align:left"><a href="mailto:commits-unsubscribe@inlong.apache.org">退订</a></td>
-<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/inlong-commits">归档</a></td>
+<td style="text-align:left"><a href="mailto:commits-subscribe@tubemq.apache.org">订阅</a></td>
+<td style="text-align:left"><a href="mailto:commits-unsubscribe@tubemq.apache.org">退订</a></td>
+<td style="text-align:left"><a href="http://mail-archives.apache.org/mod_mbox/tubemq-commits">归档</a></td>
</tr>
</tbody>
</table>
<h2>2. 订阅邮件列表</h2>
-<p><strong>以订阅dev@inlong.apache.org邮件列表为例</strong></p>
+<p><strong>以订阅dev@tubemq.apache.org邮件列表为例</strong></p>
<p>具体步骤如下：</p>
<ol>
-<li>发送一封不包含任何内容或主题的邮件到: <code>dev-subscribe@inlong.apache.org</code></li>
-<li>等待直到收到一封主题为 <code>confirm subscribe to dev@inlong.apache.org</code> 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）</li>
+<li>发送一封不包含任何内容或主题的邮件到: <code>dev-subscribe@tubemq.apache.org</code></li>
+<li>等待直到收到一封主题为 <code>confirm subscribe to dev@tubemq.apache.org</code> 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）</li>
<li>直接回复该邮件，不用修改主题和添加邮件内容。</li>
-<li>等待直到收到一封主题为 <code>WELCOME to dev@inlong.apache.org</code> 的邮件。</li>
-<li>收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往<code>dev@inlong.apache.org</code>发送邮件即可，所有订阅了邮件列表的人都会收到邮件。</li>
+<li>等待直到收到一封主题为 <code>WELCOME to dev@tubemq.apache.org</code> 的邮件。</li>
+<li>收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往<code>dev@tubemq.apache.org</code>发送邮件即可，所有订阅了邮件列表的人都会收到邮件。</li>
</ol>
<h2>3. 退订邮件列表</h2>
<p>退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：</p>
<ol>
-<li>发送一封不包含任何内容或主题的邮件到: <code>dev-unsubscribe@inlong.apache.org</code></li>
-<li>等待直到收到一封主题为 <code>confirm unsubscribe from dev@inlong.apache.org</code> 的邮件</li>
+<li>发送一封不包含任何内容或主题的邮件到: <code>dev-unsubscribe@tubemq.apache.org</code></li>
+<li>等待直到收到一封主题为 <code>confirm unsubscribe from dev@tubemq.apache.org</code> 的邮件</li>
<li>直接回复该邮件，不用修改主题和添加邮件内容</li>
-<li>等待直到收到一封主题为 <code>GOODBYE from dev@inlong.apache.org</code>的邮件</li>
+<li>等待直到收到一封主题为 <code>GOODBYE from dev@tubemq.apache.org</code>的邮件</li>
<li>退订成功</li>
</ol>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
diff --git a/en-us/docs/development/how-to-subscribe.json b/en-us/docs/development/how-to-subscribe.json
index 39b4180..6d96268 100644
--- a/en-us/docs/development/how-to-subscribe.json
+++ b/en-us/docs/development/how-to-subscribe.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-subscribe.md",
- "__html": "<h1>订阅邮件列表</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>1. 前言</h2>\n<p>邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，\n订阅邮件后，你可以第一时间获取inlong社区的动态，可以与社区保持同步。</p>\n<h4>inlong项目邮件列表</h4>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">名称</th>\n<th style=\"text-align:left\">描述</th>\n<th style=\"text-align:left\">订阅邮件</th>\n<th style [...]
+ "__html": "<h1>订阅邮件列表</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>1. 前言</h2>\n<p>邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，\n订阅邮件后，你可以第一时间获取TubeMQ社区的动态，可以与社区保持同步。</p>\n<h4>TubeMQ项目邮件列表</h4>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:left\">名称</th>\n<th style=\"text-align:left\">描述</th>\n<th style=\"text-align:left\">订阅邮件</th>\n<th style [...]
"link": "/en-us/docs/development/how-to-subscribe.html",
"meta": {
- "title": "Subscribe Mailing list - Apache inlong"
+ "title": "Subscribe Mailing list - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-subscribe.md b/en-us/docs/development/how-to-subscribe.md
index 3d70e0b..abdb85f 100644
--- a/en-us/docs/development/how-to-subscribe.md
+++ b/en-us/docs/development/how-to-subscribe.md
@@ -1,5 +1,5 @@
---
-title: Subscribe Mailing list - Apache inlong
+title: Subscribe Mailing list - Apache TubeMQ
---
# 订阅邮件列表
@@ -8,31 +8,31 @@ title: Subscribe Mailing list - Apache inlong
## 1. 前言
邮件列表是Apache社区用来沟通交流的一种形式，通常来说，Apache社区的许多事情都是由邮件列表来承载，比如：项目的提问与解答、技术讨论、事务决策、版本发布投票等等，
-订阅邮件后，你可以第一时间获取inlong社区的动态，可以与社区保持同步。
+订阅邮件后，你可以第一时间获取TubeMQ社区的动态，可以与社区保持同步。
-#### inlong项目邮件列表
+#### TubeMQ项目邮件列表
|名称|描述|订阅邮件|退订邮件|邮件归档|
|:-----|:--------|:------|:-------|:-----|
-| [dev@inlong.apache.org](mailto:dev@inlong.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@inlong.apache.org) | [退订](mailto:dev-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-dev) |
-| [commits@inlong.apache.org](mailto:commits@inlong.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@inlong.apache.org) | [退订](mailto:commits-unsubscribe@inlong.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/inlong-commits) |
+| [dev@tubemq.apache.org](mailto:dev@tubemq.apache.org) | 社区活动信息 | [订阅](mailto:dev-subscribe@tubemq.apache.org) | [退订](mailto:dev-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-dev) |
+| [commits@tubemq.apache.org](mailto:commits@tubemq.apache.org) | 代码库更新信息 | [订阅](mailto:commits-subscribe@tubemq.apache.org) | [退订](mailto:commits-unsubscribe@tubemq.apache.org) | [归档](http://mail-archives.apache.org/mod_mbox/tubemq-commits) |
## 2. 订阅邮件列表
-**以订阅dev@inlong.apache.org邮件列表为例**
+**以订阅dev@tubemq.apache.org邮件列表为例**
具体步骤如下：
- 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@inlong.apache.org`
- 2. 等待直到收到一封主题为 `confirm subscribe to dev@inlong.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
+ 1. 发送一封不包含任何内容或主题的邮件到: `dev-subscribe@tubemq.apache.org`
+ 2. 等待直到收到一封主题为 `confirm subscribe to dev@tubemq.apache.org` 的邮件(如果长时间未能收到，请确认该邮件是否被你的邮箱拦截，确定没有被拦截且长时间会收到回复邮件的话，返回第1步）
3. 直接回复该邮件，不用修改主题和添加邮件内容。
- 4. 等待直到收到一封主题为 `WELCOME to dev@inlong.apache.org` 的邮件。
- 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@inlong.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
+ 4. 等待直到收到一封主题为 `WELCOME to dev@tubemq.apache.org` 的邮件。
+ 5. 收到(4)的邮件后，就说明订阅邮件成功，若想发起讨论，直接往`dev@tubemq.apache.org`发送邮件即可，所有订阅了邮件列表的人都会收到邮件。
## 3. 退订邮件列表
退订邮件列表的步骤与订阅邮件列表类似，具体步骤如下：
-1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@inlong.apache.org`
-2. 等待直到收到一封主题为 `confirm unsubscribe from dev@inlong.apache.org` 的邮件
+1. 发送一封不包含任何内容或主题的邮件到: `dev-unsubscribe@tubemq.apache.org`
+2. 等待直到收到一封主题为 `confirm unsubscribe from dev@tubemq.apache.org` 的邮件
3. 直接回复该邮件，不用修改主题和添加邮件内容
-4. 等待直到收到一封主题为 `GOODBYE from dev@inlong.apache.org`的邮件
+4. 等待直到收到一封主题为 `GOODBYE from dev@tubemq.apache.org`的邮件
5. 退订成功
diff --git a/en-us/docs/development/how-to-use-jira.html b/en-us/docs/development/how-to-use-jira.html
index 6c9fe45..577c00c 100644
--- a/en-us/docs/development/how-to-use-jira.html
+++ b/en-us/docs/development/how-to-use-jira.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="how-to-use-jira" />
<meta name="description" content="how-to-use-jira" />
<!-- 网页标签标题 -->
- <title>How to Use JIRA - Apache inlong</title>
+ <title>How to Use JIRA - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -16,18 +16,18 @@
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<h2>0. 前言</h2>
<p>JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于
-项目的管理，基于此inlong项目同样使用JIRA来进行管理项目。本文将简单介绍在inlong的开发过程中如何使用JIRA。</p>
+项目的管理，基于此TubeMQ项目同样使用JIRA来进行管理项目。本文将简单介绍在TubeMQ的开发过程中如何使用JIRA。</p>
<h2>1. 注册并登陆到JIRA</h2>
<p>对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：</p>
<ol>
<li>登录<a href="https://issues.apache.org/jira/secure/Signup!default.jspa">注册</a>页面</li>
<li>填入个人邮箱，姓名等注册信息后即可注册。</li>
-<li>注册成功后登录并进入inlong项目。</li>
+<li>注册成功后登录并进入TubeMQ项目。</li>
</ol>
<h2>2. 查看issues</h2>
<ol>
-<li>打开<a href="https://issues.apache.org/jira/projects/inlong/issues">inlong</a>项目页面</li>
-<li>可以看到inlong项目的所有issue</li>
+<li>打开<a href="https://issues.apache.org/jira/projects/TUBEMQ/issues">TubeMQ</a>项目页面</li>
+<li>可以看到TubeMQ项目的所有issue</li>
<li>点击右上角<code>View all issues and filters</code>即可进行过滤issue，默认过滤规则包括任务类型、任务状态、负责人及输入关键字等搜索，
也点击右侧的<code>More</code>按钮，进行更多字段的过滤筛选。
<img src="../img/development/jira_filter.png" alt=""></li>
@@ -39,7 +39,7 @@
<ul>
<li>必填项
<ul>
-<li>Project: Apache inlong</li>
+<li>Project: Apache TubeMQ</li>
<li>Issue Type: 选择issue类型，包含：Task, Bug, Feature, Improvement等</li>
<li>Summary: issue标题，一句话描述该issue所要表达的问题</li>
<li>Reporter: issue的提交者，即本人</li>
@@ -60,9 +60,9 @@
</li>
</ul>
<p>创建好issue后可以将issue指定给自己或者其他人或者为空。如果指定给自己，此时你就可以准备开发代码解决该问题了。</p>
-<p><strong>如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@inlong.apache.org或联系inlong的PPMC申请加入inlong的contributor列表，加入后即可Assign其他issue给自己</strong></p>
+<p><strong>如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@tubemq.apache.org或联系TubeMQ的PPMC申请加入TubeMQ的contributor列表，加入后即可Assign其他issue给自己</strong></p>
<h2>4. 关闭issues</h2>
-<p>当该issue被解决后，可以关闭该issue，<strong>一般由inlong的PPMC和Committer来关闭issue</strong>。</p>
+<p>当该issue被解决后，可以关闭该issue，<strong>一般由TubeMQ的PPMC和Committer来关闭issue</strong>。</p>
<h3>4.1. 点击<code>Resolve Issue</code>按钮，一般不要点击<code>Close Issue</code>,如下图所示：</h3>
<p><img src="../img/development/jira_resolve_issue_1.png" alt=""></p>
<h3>4.2. 填写<code>Resolution状态</code>、<code>修复版本</code>等信息</h3>
diff --git a/en-us/docs/development/how-to-use-jira.json b/en-us/docs/development/how-to-use-jira.json
index 7f76d9d..b85c2f7 100644
--- a/en-us/docs/development/how-to-use-jira.json
+++ b/en-us/docs/development/how-to-use-jira.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-use-jira.md",
- "__html": "<h1>JIRA使用指南</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>0. 前言</h2>\n<p>JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于\n项目的管理，基于此inlong项目同样使用JIRA来进行管理项目。本文将简单介绍在inlong的开发过程中如何使用JIRA。</p>\n<h2>1. 注册并登陆到JIRA</h2>\n<p>对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：</p>\n<ol>\n<li>登录<a href=\"https://issues.apache.org/jira/secure/Signup!default.jspa\">注册</a>页面</li>\n<li>填入个人 [...]
+ "__html": "<h1>JIRA使用指南</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<h2>0. 前言</h2>\n<p>JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于\n项目的管理，基于此TubeMQ项目同样使用JIRA来进行管理项目。本文将简单介绍在TubeMQ的开发过程中如何使用JIRA。</p>\n<h2>1. 注册并登陆到JIRA</h2>\n<p>对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：</p>\n<ol>\n<li>登录<a href=\"https://issues.apache.org/jira/secure/Signup!default.jspa\">注册</a>页面</li>\n<li>填入个人 [...]
"link": "/en-us/docs/development/how-to-use-jira.html",
"meta": {
- "title": "How to Use JIRA - Apache inlong"
+ "title": "How to Use JIRA - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-use-jira.md b/en-us/docs/development/how-to-use-jira.md
index 952e8e4..bd09898 100644
--- a/en-us/docs/development/how-to-use-jira.md
+++ b/en-us/docs/development/how-to-use-jira.md
@@ -1,5 +1,5 @@
---
-title: How to Use JIRA - Apache inlong
+title: How to Use JIRA - Apache TubeMQ
---
# JIRA使用指南
@@ -8,17 +8,17 @@ title: How to Use JIRA - Apache inlong
## 0. 前言
JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目用于缺陷跟踪、需求收集、任务跟踪，其丰富的功能更加便于
-项目的管理，基于此inlong项目同样使用JIRA来进行管理项目。本文将简单介绍在inlong的开发过程中如何使用JIRA。
+项目的管理，基于此TubeMQ项目同样使用JIRA来进行管理项目。本文将简单介绍在TubeMQ的开发过程中如何使用JIRA。
## 1. 注册并登陆到JIRA
对于新用户而言，使用JIRA前需要注册一个个人账号。步骤如下：
1. 登录[注册](https://issues.apache.org/jira/secure/Signup!default.jspa)页面
2. 填入个人邮箱，姓名等注册信息后即可注册。
-3. 注册成功后登录并进入inlong项目。
+3. 注册成功后登录并进入TubeMQ项目。
## 2. 查看issues
-1. 打开[inlong](https://issues.apache.org/jira/projects/inlong/issues)项目页面
-2. 可以看到inlong项目的所有issue
+1. 打开[TubeMQ](https://issues.apache.org/jira/projects/TUBEMQ/issues)项目页面
+2. 可以看到TubeMQ项目的所有issue
3. 点击右上角`View all issues and filters`即可进行过滤issue，默认过滤规则包括任务类型、任务状态、负责人及输入关键字等搜索，
也点击右侧的`More`按钮，进行更多字段的过滤筛选。
@@ -29,7 +29,7 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
- 必填项
- - Project: Apache inlong
+ - Project: Apache TubeMQ
- Issue Type: 选择issue类型，包含：Task, Bug, Feature, Improvement等
- Summary: issue标题，一句话描述该issue所要表达的问题
- Reporter: issue的提交者，即本人
@@ -43,10 +43,10 @@ JIRA是Apache官方推荐的任务管理平台，被Apache下的大部分项目
创建好issue后可以将issue指定给自己或者其他人或者为空。如果指定给自己，此时你就可以准备开发代码解决该问题了。
-**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@inlong.apache.org或联系inlong的PPMC申请加入inlong的contributor列表，加入后即可Assign其他issue给自己**
+**如果你是第一次提交issue，可能该issue无法Assign给自己，此时你可以发邮件至：dev@tubemq.apache.org或联系TubeMQ的PPMC申请加入TubeMQ的contributor列表，加入后即可Assign其他issue给自己**
## 4. 关闭issues
-当该issue被解决后，可以关闭该issue，**一般由inlong的PPMC和Committer来关闭issue**。
+当该issue被解决后，可以关闭该issue，**一般由TubeMQ的PPMC和Committer来关闭issue**。
### 4.1. 点击`Resolve Issue`按钮，一般不要点击`Close Issue`,如下图所示：
diff --git a/en-us/docs/development/how-to-verify.html b/en-us/docs/development/how-to-verify.html
index ac972c0..20d76bf 100644
--- a/en-us/docs/development/how-to-verify.html
+++ b/en-us/docs/development/how-to-verify.html
@@ -7,7 +7,7 @@
<meta name="keywords" content="how-to-verify" />
<meta name="description" content="how-to-verify" />
<!-- 网页标签标题 -->
- <title>How to Verify - Apache inlong</title>
+ <title>How to Verify - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
@@ -16,7 +16,7 @@
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<p>详细的检查列表请参考: <a href="https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist">check list</a></p>
<h2>1. 下载要发布的候选版本到本地环境</h2>
-<pre><code class="language-shell">svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+<pre><code class="language-shell">svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
</code></pre>
<h2>2. 验证上传的版本是否合规</h2>
<blockquote>
@@ -36,7 +36,7 @@
<ul>
<li>导入公钥</li>
</ul>
-<pre><code class="language-shell">curl https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS > KEYS # 下载KEYS
+<pre><code class="language-shell">curl https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS > KEYS # 下载KEYS
gpg --import KEYS # 导入KEYS到本地
</code></pre>
<ul>
@@ -101,10 +101,10 @@ gpg --import KEYS # 导入KEYS到本地
</ul>
<pre><code class="language-shell">for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
<span class="hljs-meta">#</span><span class="bash">或者</span>
-gpg --verify apache-inlong-${release_version}-src.tar.gz.asc apache-inlong-${release_version}-src.tar.gz
+gpg --verify apache-tubemq-${release_version}-src.tar.gz.asc apache-tubemq-${release_version}-src.tar.gz
<span class="hljs-meta">#</span><span class="bash"> 如果上传二进制包，则同样需要检查二进制包的签名是否正确</span>
-gpg --verify apache-inlong-server-${release_version}-bin.tar.gz.asc apache-inlong-server-${release_version}-bin.tar.gz
-gpg --verify apache-inlong-client-${release_version}-bin.tar.gz.asc apache-inlong-client-${release_version}-bin.tar.gz
+gpg --verify apache-tubemq-server-${release_version}-bin.tar.gz.asc apache-tubemq-server-${release_version}-bin.tar.gz
+gpg --verify apache-tubemq-client-${release_version}-bin.tar.gz.asc apache-tubemq-client-${release_version}-bin.tar.gz
</code></pre>
<ul>
<li>检查结果</li>
@@ -112,7 +112,7 @@ gpg --verify apache-inlong-client-${release_version}-bin.tar.gz.asc apache-inlon
<blockquote>
<p>出现类似以下内容则说明签名正确，关键字：<strong><code>Good signature</code></strong></p>
</blockquote>
-<pre><code class="language-shell">apache-inlong-0.3.0-incubating-src.tar.gz
+<pre><code class="language-shell">apache-tubemq-0.3.0-incubating-src.tar.gz
gpg: Signature made Sat May 30 11:45:01 2020 CST
gpg: using RSA key 9B12C2228BDFF4F4CFE849445EF3A66D57EC647A
gpg: Good signature from "Guangxu Cheng <gxcheng@apache.org>" [ultimate]gular2
@@ -123,15 +123,15 @@ gpg: Good signature from "Guangxu Cheng <gxcheng@apache.org>" [ultimate]gu
</blockquote>
<pre><code class="language-shell">for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i; done
<span class="hljs-meta">#</span><span class="bash">或者</span>
-gpg --print-md SHA512 apache-inlong-${release_version}-src.tar.gz
+gpg --print-md SHA512 apache-tubemq-${release_version}-src.tar.gz
<span class="hljs-meta">#</span><span class="bash"> 如果上传二进制包，则同样需要检查二进制包的sha512哈希</span>
-gpg --print-md SHA512 apache-inlong-server-${release_version}-bin.tar.gz
-gpg --print-md SHA512 apache-inlong-client-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-server-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-client-${release_version}-bin.tar.gz
<span class="hljs-meta">#</span><span class="bash"> 或者</span>
for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
</code></pre>
<h3>2.4. 检查源码包的文件内容</h3>
-<p>解压缩<code>apache-inlong-${release_version}-src.tar.gz</code>，进行如下检查:</p>
+<p>解压缩<code>apache-tubemq-${release_version}-src.tar.gz</code>，进行如下检查:</p>
<ul>
<li>DISCLAIMER文件是否存在及内容是否正确</li>
<li>LICENSE and NOTICE文件是否存在及内容是否正确</li>
@@ -141,7 +141,7 @@ for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
<li>....</li>
</ul>
<h3>2.5 检查二进制包(如果上传了二进制包)</h3>
-<p>解压缩<code>apache-inlong-client-${release_version}-src.tar.gz</code>和<code>apache-inlong-server-${release_version}-src.tar.gz</code>，进行如下检查:</p>
+<p>解压缩<code>apache-tubemq-client-${release_version}-src.tar.gz</code>和<code>apache-tubemq-server-${release_version}-src.tar.gz</code>，进行如下检查:</p>
<ul>
<li>DISCLAIMER文件是否存在及内容是否正确</li>
<li>LICENSE and NOTICE文件是否存在及内容是否正确</li>
diff --git a/en-us/docs/development/how-to-verify.json b/en-us/docs/development/how-to-verify.json
index 189a519..58274ca 100644
--- a/en-us/docs/development/how-to-verify.json
+++ b/en-us/docs/development/how-to-verify.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-verify.md",
- "__html": "<h1>验证候选版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<p>详细的检查列表请参考: <a href=\"https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist\">check list</a></p>\n<h2>1. 下载要发布的候选版本到本地环境</h2>\n<pre><code class=\"language-shell\">svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/\n</code></pre>\n<h2>2. 验证上传的版本是否合 [...]
+ "__html": "<h1>验证候选版本</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<p>详细的检查列表请参考: <a href=\"https://cwiki.apache.org/confluence/display/INCUBATOR/Incubator+Release+Checklist\">check list</a></p>\n<h2>1. 下载要发布的候选版本到本地环境</h2>\n<pre><code class=\"language-shell\">svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/\n</code></pre>\n<h2>2. 验证上传的版本是否合 [...]
"link": "/en-us/docs/development/how-to-verify.html",
"meta": {
- "title": "How to Verify - Apache inlong"
+ "title": "How to Verify - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-verify.md b/en-us/docs/development/how-to-verify.md
index 3d856d7..e8dae4d 100644
--- a/en-us/docs/development/how-to-verify.md
+++ b/en-us/docs/development/how-to-verify.md
@@ -1,5 +1,5 @@
---
-title: How to Verify - Apache inlong
+title: How to Verify - Apache TubeMQ
---
# 验证候选版本
@@ -10,7 +10,7 @@ title: How to Verify - Apache inlong
## 1. 下载要发布的候选版本到本地环境
```shell
-svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version}-${rc_version}/
+svn co https://dist.apache.org/repos/dist/dev/incubator/tubemq/${release_version}-${rc_version}/
```
## 2. 验证上传的版本是否合规
> 开始验证环节，验证包含但不局限于以下内容和形式
@@ -26,7 +26,7 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
### 2.2 检查gpg签名
- 导入公钥
```shell
- curl https://dist.apache.org/repos/dist/dev/incubator/inlong/KEYS > KEYS # 下载KEYS
+ curl https://dist.apache.org/repos/dist/dev/incubator/tubemq/KEYS > KEYS # 下载KEYS
gpg --import KEYS # 导入KEYS到本地
```
- 信任公钥
@@ -87,15 +87,15 @@ svn co https://dist.apache.org/repos/dist/dev/incubator/inlong/${release_version
```shell
for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
#或者
- gpg --verify apache-inlong-${release_version}-src.tar.gz.asc apache-inlong-${release_version}-src.tar.gz
+ gpg --verify apache-tubemq-${release_version}-src.tar.gz.asc apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的签名是否正确
- gpg --verify apache-inlong-server-${release_version}-bin.tar.gz.asc apache-inlong-server-${release_version}-bin.tar.gz
- gpg --verify apache-inlong-client-${release_version}-bin.tar.gz.asc apache-inlong-client-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-server-${release_version}-bin.tar.gz.asc apache-tubemq-server-${release_version}-bin.tar.gz
+ gpg --verify apache-tubemq-client-${release_version}-bin.tar.gz.asc apache-tubemq-client-${release_version}-bin.tar.gz
```
- 检查结果
> 出现类似以下内容则说明签名正确，关键字：**`Good signature`**
```shell
-apache-inlong-0.3.0-incubating-src.tar.gz
+apache-tubemq-0.3.0-incubating-src.tar.gz
gpg: Signature made Sat May 30 11:45:01 2020 CST
gpg: using RSA key 9B12C2228BDFF4F4CFE849445EF3A66D57EC647A
gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
@@ -106,17 +106,17 @@ gpg: Good signature from "Guangxu Cheng <gx...@apache.org>" [ultimate]gular2
```shell
for i in *.tar.gz; do echo $i; gpg --print-md SHA512 $i; done
#或者
-gpg --print-md SHA512 apache-inlong-${release_version}-src.tar.gz
+gpg --print-md SHA512 apache-tubemq-${release_version}-src.tar.gz
# 如果上传二进制包，则同样需要检查二进制包的sha512哈希
-gpg --print-md SHA512 apache-inlong-server-${release_version}-bin.tar.gz
-gpg --print-md SHA512 apache-inlong-client-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-server-${release_version}-bin.tar.gz
+gpg --print-md SHA512 apache-tubemq-client-${release_version}-bin.tar.gz
# 或者
for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
```
### 2.4. 检查源码包的文件内容
- 解压缩`apache-inlong-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
@@ -126,8 +126,8 @@ for i in *.tar.gz.sha512; do echo $i; sha512sum -c $i; done
- ....
### 2.5 检查二进制包(如果上传了二进制包)
- 解压缩`apache-inlong-client-${release_version}-src.tar.gz`和`
- apache-inlong-server-${release_version}-src.tar.gz`，进行如下检查:
+ 解压缩`apache-tubemq-client-${release_version}-src.tar.gz`和`
+ apache-tubemq-server-${release_version}-src.tar.gz`，进行如下检查:
- DISCLAIMER文件是否存在及内容是否正确
- LICENSE and NOTICE文件是否存在及内容是否正确
- 能否正常部署成功
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.html b/en-us/docs/development/how-to-vote-a-committer-ppmc.html
index 9f7b433..4184690 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.html
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.html
@@ -7,40 +7,40 @@
<meta name="keywords" content="how-to-vote-a-committer-ppmc" />
<meta name="description" content="how-to-vote-a-committer-ppmc" />
<!-- 网页标签标题 -->
- <title>How to vote a Committer or PPMC - Apache inlong</title>
+ <title>How to vote a Committer or PPMC - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
<p><font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>
<ol>
<li>
-<p>inlong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在inlong的private邮件列表发起讨论；</p>
+<p>TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在TubeMQ的private邮件列表发起讨论；</p>
<blockquote>
-<p>[DISCUSS] YYYYY as a inlong XXXXXX</p>
+<p>[DISCUSS] YYYYY as a TubeMQ XXXXXX</p>
</blockquote>
<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>
</li>
<li>
-<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在inlong的private邮件列表发起Committer或PPMC的选举投票；</p>
+<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在TubeMQ的private邮件列表发起Committer或PPMC的选举投票；</p>
<blockquote>
-<p>[VOTE] YYYYY as a inlong XXXXXX</p>
+<p>[VOTE] YYYYY as a TubeMQ XXXXXX</p>
</blockquote>
<p>投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1票则投票失败；如果-1，需要把问题说清楚，便于大家理解和知晓</p>
</li>
<li>
<p>投票邮件结束后，由投票发起者在投票线上总结并提醒投票结束，并发投票总结邮件；</p>
<blockquote>
-<p>[RESULTS][VOTE] YYYYY as a inlong XXXXXX</p>
+<p>[RESULTS][VOTE] YYYYY as a TubeMQ XXXXXX</p>
</blockquote>
</li>
<li>
<p>投票总结邮件发出后，投票发起者要给候选人发起邀请邮件，该邀请邮件需要候选人通过指定的邮箱回复接受或者拒绝；</p>
<blockquote>
-<p>[Invitation] Invitation to join Apache inlong as a XXXXXX</p>
+<p>[Invitation] Invitation to join Apache TubeMQ as a XXXXXX</p>
</blockquote>
-<p>邮件主送邀请人，抄送private@inlong.apache.org</p>
+<p>邮件主送邀请人，抄送private@tubemq.apache.org</p>
</li>
<li>
<p>候选人接受邀请后，如果候选人没有apache邮箱帐号，投票发起者需要协助候选人按照指引创建apache帐号；</p>
@@ -48,14 +48,14 @@
<li>
<p>如果选举的是PPMC，在候选人的Apache帐号创建完成后，投票发起者还需要向IPMC的private邮件组发送知会邮件，并等待至少72小时;</p>
<blockquote>
-<p>[NOTICE] XXXXXX for inlong PPMC</p>
+<p>[NOTICE] XXXXXX for TubeMQ PPMC</p>
</blockquote>
-<p>邮件主送private@incubator.apache.org，抄送private@inlong.apache.org，IPMC们会分析合规性，直到没有疑义。</p>
+<p>邮件主送private@incubator.apache.org，抄送private@tubemq.apache.org，IPMC们会分析合规性，直到没有疑义。</p>
</li>
<li>
<p>如果以上内容都以完成，投票发起者还需要做如下2件事情：
7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。</p>
-<p>7.2 向dev@inlong.apache.org邮件组发通知邮件：</p>
+<p>7.2 向dev@tubemq.apache.org邮件组发通知邮件：</p>
<blockquote>
<pre><code> [ANNOUNCE] New XXXXXX: YYYYY
</code></pre>
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.json b/en-us/docs/development/how-to-vote-a-committer-ppmc.json
index 6edf40e..38fae63 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.json
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.json
@@ -1,8 +1,8 @@
{
"filename": "how-to-vote-a-committer-ppmc.md",
- "__html": "<h1>成为inlong Committer 或 PPMC 的投票过程</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<ol>\n<li>\n<p>inlong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在inlong的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a inlong XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在inlong的private [...]
+ "__html": "<h1>成为TubeMQ Committer 或 PPMC 的投票过程</h1>\n<p><font color=\"#dd0000\" size=\"4\">TODO: This page needs to be translated into English. If you are interested, just do it.</font></p>\n<ol>\n<li>\n<p>TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在TubeMQ的private邮件列表发起讨论；</p>\n<blockquote>\n<p>[DISCUSS] YYYYY as a TubeMQ XXXXXX</p>\n</blockquote>\n<p>邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；</p>\n</li>\n<li>\n<p>不管有没有分歧，在讨论邮件过后，投票发起者需要在在TubeMQ的private [...]
"link": "/en-us/docs/development/how-to-vote-a-committer-ppmc.html",
"meta": {
- "title": "How to vote a Committer or PPMC - Apache inlong"
+ "title": "How to vote a Committer or PPMC - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/development/how-to-vote-a-committer-ppmc.md b/en-us/docs/development/how-to-vote-a-committer-ppmc.md
index f78b9d3..84f1c4e 100644
--- a/en-us/docs/development/how-to-vote-a-committer-ppmc.md
+++ b/en-us/docs/development/how-to-vote-a-committer-ppmc.md
@@ -1,46 +1,46 @@
---
-title: How to vote a Committer or PPMC - Apache inlong
+title: How to vote a Committer or PPMC - Apache TubeMQ
---
-# 成为inlong Committer 或 PPMC 的投票过程
+# 成为TubeMQ Committer 或 PPMC 的投票过程
<font color="#dd0000" size="4">TODO: This page needs to be translated into English. If you are interested, just do it.</font>
-1. inlong的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在inlong的private邮件列表发起讨论；
- > [DISCUSS] YYYYY as a inlong XXXXXX
+1. TubeMQ的PPMC成员发现社区贡献者任何有价值的贡献并取得候选人本人同意后，在TubeMQ的private邮件列表发起讨论；
+ > [DISCUSS] YYYYY as a TubeMQ XXXXXX
邮件里要把对方的贡献，可以查看的出处说清楚，便于大家讨论分析；讨论邮件将持续至少72个小时，项目组成员，包括mentor们会针对提议邮件充分发表自己的看法；
-2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在inlong的private邮件列表发起Committer或PPMC的选举投票；
- > [VOTE] YYYYY as a inlong XXXXXX
+2. 不管有没有分歧，在讨论邮件过后，投票发起者需要在在TubeMQ的private邮件列表发起Committer或PPMC的选举投票；
+ > [VOTE] YYYYY as a TubeMQ XXXXXX
投票邮件至少持续72小时，至少要3票+1通过，如果0票或者有1票-1票则投票失败；如果-1，需要把问题说清楚，便于大家理解和知晓
3. 投票邮件结束后，由投票发起者在投票线上总结并提醒投票结束，并发投票总结邮件；
- > [RESULTS][VOTE] YYYYY as a inlong XXXXXX
+ > [RESULTS][VOTE] YYYYY as a TubeMQ XXXXXX
4. 投票总结邮件发出后，投票发起者要给候选人发起邀请邮件，该邀请邮件需要候选人通过指定的邮箱回复接受或者拒绝；
- > [Invitation] Invitation to join Apache inlong as a XXXXXX
+ > [Invitation] Invitation to join Apache TubeMQ as a XXXXXX
- 邮件主送邀请人，抄送private@inlong.apache.org
+ 邮件主送邀请人，抄送private@tubemq.apache.org
5. 候选人接受邀请后，如果候选人没有apache邮箱帐号，投票发起者需要协助候选人按照指引创建apache帐号；
6. 如果选举的是PPMC，在候选人的Apache帐号创建完成后，投票发起者还需要向IPMC的private邮件组发送知会邮件，并等待至少72小时;
- > [NOTICE] XXXXXX for inlong PPMC
+ > [NOTICE] XXXXXX for TubeMQ PPMC
- 邮件主送private@incubator.apache.org，抄送private@inlong.apache.org，IPMC们会分析合规性，直到没有疑义。
+ 邮件主送private@incubator.apache.org，抄送private@tubemq.apache.org，IPMC们会分析合规性，直到没有疑义。
7. 如果以上内容都以完成，投票发起者还需要做如下2件事情：
7.1 向项目负责人申请添加项目组成员，开通jira及apache项目的权限帐号。
- 7.2 向dev@inlong.apache.org邮件组发通知邮件：
+ 7.2 向dev@tubemq.apache.org邮件组发通知邮件：
> [ANNOUNCE] New XXXXXX: YYYYY
diff --git a/en-us/docs/download/download.html b/en-us/docs/download/download.html
index c4ee5f5..998e0e0 100644
--- a/en-us/docs/download/download.html
+++ b/en-us/docs/download/download.html
@@ -7,52 +7,52 @@
<meta name="keywords" content="download" />
<meta name="description" content="download" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
<div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong Releases, the latest release is 0.8.0.</p>
+<p>Use the links below to download the Apache TubeMQ Releases, the latest release is 0.8.0.</p>
<h2>0.8.0 release</h2>
<ul>
<li>Released: March 4th, 2021</li>
<li><a href="release-0.8.0.md">Release Notes</a></li>
-<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz">inlong-0.8.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
-<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz">inlong-client-0.8.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
-<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz">inlong-server-0.8.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz">tubemq-0.8.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
+<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz">tubemq-client-0.8.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz">tubemq-server-0.8.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
</ul>
<h2>0.7.0 release</h2>
<ul>
<li>Released: December 4th, 2020</li>
<li><a href="release-0.7.0.md">Release Notes</a></li>
-<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz">inlong-0.7.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
-<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz">inlong-client-0.7.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
-<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz">inlong-server-0.7.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz">tubemq-0.7.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
+<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz">tubemq-client-0.7.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz">tubemq-server-0.7.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
</ul>
<h2>0.6.0 release</h2>
<ul>
<li>Released: October 21th, 2020</li>
<li><a href="release-0.6.0.md">Release Notes</a></li>
-<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz">inlong-0.6.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
-<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz">inlong-client-0.6.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
-<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz">inlong-server-0.6.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz">tubemq-0.6.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
+<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz">tubemq-client-0.6.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz">tubemq-server-0.6.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
</ul>
<h2>0.5.0 release</h2>
<ul>
<li>Released: August 4th, 2020</li>
<li><a href="release-0.5.0.md">Release Notes</a></li>
-<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz">inlong-0.5.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
-<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz">inlong-client-0.5.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
-<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz">inlong-server-0.5.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz">tubemq-0.5.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
+<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz">tubemq-client-0.5.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz">tubemq-server-0.5.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
</ul>
<h2>0.3.0 release</h2>
<ul>
<li>Released: June 6th, 2020</li>
<li><a href="release-0.3.0.md">Release Notes</a></li>
-<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz">inlong-0.3.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
-<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz">inlong-client-0.3.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
-<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz">inlong-server-0.3.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Source: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz">tubemq-0.3.0-incubating-src.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512">SHA512</a>]</li>
+<li>Client: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz">tubemq-client-0.3.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
+<li>Server: <a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz">tubemq-server-0.3.0-incubating-bin.tar.gz</a> [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</li>
</ul>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
diff --git a/en-us/docs/download/download.json b/en-us/docs/download/download.json
index 90db390..150a551 100644
--- a/en-us/docs/download/download.json
+++ b/en-us/docs/download/download.json
@@ -1,8 +1,8 @@
{
"filename": "download.md",
- "__html": "<h2>Download links</h2>\n<p>Use the links below to download the Apache inlong Releases, the latest release is 0.8.0.</p>\n<h2>0.8.0 release</h2>\n<ul>\n<li>Released: March 4th, 2021</li>\n<li><a href=\"release-0.8.0.md\">Release Notes</a></li>\n<li>Source: <a href=\"http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz\">inlong-0.8.0-incubating-src.tar.gz</a> [<a href=\"https://downloads.apache.org/incub [...]
+ "__html": "<h2>Download links</h2>\n<p>Use the links below to download the Apache TubeMQ Releases, the latest release is 0.8.0.</p>\n<h2>0.8.0 release</h2>\n<ul>\n<li>Released: March 4th, 2021</li>\n<li><a href=\"release-0.8.0.md\">Release Notes</a></li>\n<li>Source: <a href=\"http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz\">tubemq-0.8.0-incubating-src.tar.gz</a> [<a href=\"https://downloads.apache.org/incub [...]
"link": "/en-us/docs/download/download.html",
"meta": {
- "title": "Download - Apache inlong"
+ "title": "Download - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/download/download.md b/en-us/docs/download/download.md
index bd9742b..9aedbf6 100644
--- a/en-us/docs/download/download.md
+++ b/en-us/docs/download/download.md
@@ -1,44 +1,44 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
## Download links
- Use the links below to download the Apache inlong Releases, the latest release is 0.8.0.
+ Use the links below to download the Apache TubeMQ Releases, the latest release is 0.8.0.
## 0.8.0 release
- Released: March 4th, 2021
- [Release Notes](release-0.8.0.md)
- - Source: [inlong-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.8.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.8.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512)]
## 0.7.0 release
- Released: December 4th, 2020
- [Release Notes](release-0.7.0.md)
- - Source: [inlong-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.7.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.7.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)]
## 0.6.0 release
- Released: October 21th, 2020
- [Release Notes](release-0.6.0.md)
- - Source: [inlong-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.6.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.6.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)]
## 0.5.0 release
- Released: August 4th, 2020
- [Release Notes](release-0.5.0.md)
- - Source: [inlong-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.5.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.5.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)]
## 0.3.0 release
- Released: June 6th, 2020
- [Release Notes](release-0.3.0.md)
- - Source: [inlong-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)]
- - Client: [inlong-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)]
- - Server: [inlong-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)]
+ - Source: [tubemq-0.3.0-incubating-src.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)]
+ - Client: [tubemq-client-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)]
+ - Server: [tubemq-server-0.3.0-incubating-bin.tar.gz](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz) [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)]
diff --git a/en-us/docs/download/release-0.3.0.html b/en-us/docs/download/release-0.3.0.html
index b75b856..aaabe22 100644
--- a/en-us/docs/download/release-0.3.0.html
+++ b/en-us/docs/download/release-0.3.0.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="release-0.3.0" />
<meta name="description" content="release-0.3.0" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong from one of our mirrors.</p>
-<h2>inlong</h2>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>
+<h2>TubeMQ</h2>
<table>
<thead>
<tr>
@@ -29,71 +29,71 @@
<td style="text-align:center">June. 6th, 2020</td>
<td style="text-align:center">0.3.0</td>
<td style="text-align:center">Source</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Client</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Server</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
</tbody>
</table>
<h2>Release Notes</h2>
<h3>New Features</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-42">inlong-42</a>] Add peer information about message received Major New Feature</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-42">TUBEMQ-42</a>] Add peer information about message received Major New Feature</li>
</ul>
<h3>Improvements</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-7">inlong-7</a>] Using StringBuilder instead of StringBuffer in BaseResult</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-9">inlong-9</a>] Remove some unnecessary code</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-16">inlong-16</a>] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-18">inlong-18</a>] Correct TMaster#idGenerater to TMaster#idGenerator</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-19">inlong-19</a>] Correct parameter names to fit in camel case</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-20">inlong-20</a>] Correct DefaultLoadBalancer#balance parameter</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-21">inlong-21</a>] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-22">inlong-22</a>] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-23">inlong-23</a>] Improve project README content introduction</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-24">inlong-24</a>] Add NOTICE and adjust LICENSE</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-26">inlong-26</a>] correct spelling (difftime-> diffTime)</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-27">inlong-27</a>] replace StringBuffer with StringBuilder</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-28">inlong-28</a>] ignore path error</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-29">inlong-29</a>] Change the package name to org.apache.inlong.""</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-33">inlong-33</a>] refactor enum implement from annoymouse inner class</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-38">inlong-38</a>] Correct DefaultLoadBalancer#balance parameter</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-39">inlong-39</a>] Optimize the loadMessageStores() logic</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-40">inlong-40</a>] Optimize message disk store classes's logic</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-43">inlong-43</a>] Add DeletePolicy's value check</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-44">inlong-44</a>] Remove unnecessary synchronized definition of shutdown () function</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-49">inlong-49</a>] setTimeoutTime change to updTimeoutTime</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-50">inlong-50</a>] Replace fastjson to gson</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-7">TUBEMQ-7</a>] Using StringBuilder instead of StringBuffer in BaseResult</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-9">TUBEMQ-9</a>] Remove some unnecessary code</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-16">TUBEMQ-16</a>] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-18">TUBEMQ-18</a>] Correct TMaster#idGenerater to TMaster#idGenerator</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-19">TUBEMQ-19</a>] Correct parameter names to fit in camel case</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-20">TUBEMQ-20</a>] Correct DefaultLoadBalancer#balance parameter</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-21">TUBEMQ-21</a>] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-22">TUBEMQ-22</a>] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-23">TUBEMQ-23</a>] Improve project README content introduction</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-24">TUBEMQ-24</a>] Add NOTICE and adjust LICENSE</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-26">TUBEMQ-26</a>] correct spelling (difftime-> diffTime)</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-27">TUBEMQ-27</a>] replace StringBuffer with StringBuilder</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-28">TUBEMQ-28</a>] ignore path error</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-29">TUBEMQ-29</a>] Change the package name to org.apache.tubemq.""</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-33">TUBEMQ-33</a>] refactor enum implement from annoymouse inner class</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-38">TUBEMQ-38</a>] Correct DefaultLoadBalancer#balance parameter</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-39">TUBEMQ-39</a>] Optimize the loadMessageStores() logic</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-40">TUBEMQ-40</a>] Optimize message disk store classes's logic</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-43">TUBEMQ-43</a>] Add DeletePolicy's value check</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-44">TUBEMQ-44</a>] Remove unnecessary synchronized definition of shutdown () function</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-49">TUBEMQ-49</a>] setTimeoutTime change to updTimeoutTime</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-50">TUBEMQ-50</a>] Replace fastjson to gson</li>
</ul>
<h3>Bug Fixes</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-10">inlong-10</a>] Fix Javadoc error</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-14">inlong-14</a>] Some compilation errors</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-15">inlong-15</a>] Correct typo in http_access_API_definition.md</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-32">inlong-32</a>] File path not match with package name in inlong-client module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-35">inlong-35</a>] check illegal package's field value</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-36">inlong-36</a>] Remove unnecessary removefirst() function printing</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-37">inlong-37</a>] Offset is set to 0 when Broker goes offline</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-45">inlong-45</a>] Check groupName with checkHostName function</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-48">inlong-48</a>] No timeout when setting consumer timeout</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-59">inlong-59</a>] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-62">inlong-62</a>] consumed and set consumerConfig.setConsumeModel (0) for the first time</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-66">inlong-66</a>] TubeSingleSessionFactory shutdown bug</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-85">inlong-85</a>] There is NPE when creating PullConsumer with TubeSingleSessionFactory</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-88">inlong-88</a>] Broker does not take effect after the deletePolicy value is changed</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-149">inlong-149</a>] Some of the consumers stop consuming their corresponding partitions and never release the partition to others</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-153">inlong-153</a>] Some of the consumers stop consuming their corresponding partitions and never release the partition to others</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-165">inlong-165</a>] Remove unnecessary fiiles</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-10">TUBEMQ-10</a>] Fix Javadoc error</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-14">TUBEMQ-14</a>] Some compilation errors</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-15">TUBEMQ-15</a>] Correct typo in http_access_API_definition.md</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-32">TUBEMQ-32</a>] File path not match with package name in tubemq-client module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-35">TUBEMQ-35</a>] check illegal package's field value</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-36">TUBEMQ-36</a>] Remove unnecessary removefirst() function printing</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-37">TUBEMQ-37</a>] Offset is set to 0 when Broker goes offline</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-45">TUBEMQ-45</a>] Check groupName with checkHostName function</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-48">TUBEMQ-48</a>] No timeout when setting consumer timeout</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-59">TUBEMQ-59</a>] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-62">TUBEMQ-62</a>] consumed and set consumerConfig.setConsumeModel (0) for the first time</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-66">TUBEMQ-66</a>] TubeSingleSessionFactory shutdown bug</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-85">TUBEMQ-85</a>] There is NPE when creating PullConsumer with TubeSingleSessionFactory</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-88">TUBEMQ-88</a>] Broker does not take effect after the deletePolicy value is changed</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-149">TUBEMQ-149</a>] Some of the consumers stop consuming their corresponding partitions and never release the partition to others</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-153">TUBEMQ-153</a>] Some of the consumers stop consuming their corresponding partitions and never release the partition to others</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-165">TUBEMQ-165</a>] Remove unnecessary fiiles</li>
</ul>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
diff --git a/en-us/docs/download/release-0.3.0.json b/en-us/docs/download/release-0.3.0.json
index f377b23..d98371b 100644
--- a/en-us/docs/download/release-0.3.0.json
+++ b/en-us/docs/download/release-0.3.0.json
@@ -1,8 +1,8 @@
{
"filename": "release-0.3.0.md",
- "__html": "<h1>Download the inlong releases</h1>\n<p>Use the links below to download the Apache inlong from one of our mirrors.</p>\n<h2>inlong</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">June. 6th, 2020</td>\n<td style=\"text-align:center\">0.3.0</td>\n<td [...]
+ "__html": "<h1>Download the TubeMQ releases</h1>\n<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>\n<h2>TubeMQ</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">June. 6th, 2020</td>\n<td style=\"text-align:center\">0.3.0</td>\n<td [...]
"link": "/en-us/docs/download/release-0.3.0.html",
"meta": {
- "title": "Download - Apache inlong"
+ "title": "Download - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.3.0.md b/en-us/docs/download/release-0.3.0.md
index 7b200b6..9184528 100644
--- a/en-us/docs/download/release-0.3.0.md
+++ b/en-us/docs/download/release-0.3.0.md
@@ -1,65 +1,65 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| June. 6th, 2020 | 0.3.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-0.3.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-client-0.3.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.3.0-incubating/apache-inlong-server-0.3.0-incubating-bin.tar.gz.sha512)] |
+| June. 6th, 2020 | 0.3.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-0.3.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-client-0.3.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.3.0-incubating/apache-tubemq-server-0.3.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
- - [[inlong-42](https://issues.apache.org/jira/browse/inlong-42)] Add peer information about message received Major New Feature
+ - [[TUBEMQ-42](https://issues.apache.org/jira/browse/TUBEMQ-42)] Add peer information about message received Major New Feature
### Improvements
- - [[inlong-7](https://issues.apache.org/jira/browse/inlong-7)] Using StringBuilder instead of StringBuffer in BaseResult
- - [[inlong-9](https://issues.apache.org/jira/browse/inlong-9)] Remove some unnecessary code
- - [[inlong-16](https://issues.apache.org/jira/browse/inlong-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
- - [[inlong-18](https://issues.apache.org/jira/browse/inlong-18)] Correct TMaster#idGenerater to TMaster#idGenerator
- - [[inlong-19](https://issues.apache.org/jira/browse/inlong-19)] Correct parameter names to fit in camel case
- - [[inlong-20](https://issues.apache.org/jira/browse/inlong-20)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-21](https://issues.apache.org/jira/browse/inlong-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
- - [[inlong-22](https://issues.apache.org/jira/browse/inlong-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
- - [[inlong-23](https://issues.apache.org/jira/browse/inlong-23)] Improve project README content introduction
- - [[inlong-24](https://issues.apache.org/jira/browse/inlong-24)] Add NOTICE and adjust LICENSE
- - [[inlong-26](https://issues.apache.org/jira/browse/inlong-26)] correct spelling (difftime-> diffTime)
- - [[inlong-27](https://issues.apache.org/jira/browse/inlong-27)] replace StringBuffer with StringBuilder
- - [[inlong-28](https://issues.apache.org/jira/browse/inlong-28)] ignore path error
- - [[inlong-29](https://issues.apache.org/jira/browse/inlong-29)] Change the package name to org.apache.inlong.""
- - [[inlong-33](https://issues.apache.org/jira/browse/inlong-33)] refactor enum implement from annoymouse inner class
- - [[inlong-38](https://issues.apache.org/jira/browse/inlong-38)] Correct DefaultLoadBalancer#balance parameter
- - [[inlong-39](https://issues.apache.org/jira/browse/inlong-39)] Optimize the loadMessageStores() logic
- - [[inlong-40](https://issues.apache.org/jira/browse/inlong-40)] Optimize message disk store classes's logic
- - [[inlong-43](https://issues.apache.org/jira/browse/inlong-43)] Add DeletePolicy's value check
- - [[inlong-44](https://issues.apache.org/jira/browse/inlong-44)] Remove unnecessary synchronized definition of shutdown () function
- - [[inlong-49](https://issues.apache.org/jira/browse/inlong-49)] setTimeoutTime change to updTimeoutTime
- - [[inlong-50](https://issues.apache.org/jira/browse/inlong-50)] Replace fastjson to gson
+ - [[TUBEMQ-7](https://issues.apache.org/jira/browse/TUBEMQ-7)] Using StringBuilder instead of StringBuffer in BaseResult
+ - [[TUBEMQ-9](https://issues.apache.org/jira/browse/TUBEMQ-9)] Remove some unnecessary code
+ - [[TUBEMQ-16](https://issues.apache.org/jira/browse/TUBEMQ-16)] Correct BdbStoreService#isPrimaryNodeActived to BdbStoreService#isPrimaryNodeActive
+ - [[TUBEMQ-18](https://issues.apache.org/jira/browse/TUBEMQ-18)] Correct TMaster#idGenerater to TMaster#idGenerator
+ - [[TUBEMQ-19](https://issues.apache.org/jira/browse/TUBEMQ-19)] Correct parameter names to fit in camel case
+ - [[TUBEMQ-20](https://issues.apache.org/jira/browse/TUBEMQ-20)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-21](https://issues.apache.org/jira/browse/TUBEMQ-21)] Change version number from x.y-SNAPSHOT to x.y.z-incubating-SNAPSHOT
+ - [[TUBEMQ-22](https://issues.apache.org/jira/browse/TUBEMQ-22)] Correct ClientSubInfo#getTopicProcesser -> ClientSubInfo#getTopicProcessor
+ - [[TUBEMQ-23](https://issues.apache.org/jira/browse/TUBEMQ-23)] Improve project README content introduction
+ - [[TUBEMQ-24](https://issues.apache.org/jira/browse/TUBEMQ-24)] Add NOTICE and adjust LICENSE
+ - [[TUBEMQ-26](https://issues.apache.org/jira/browse/TUBEMQ-26)] correct spelling (difftime-> diffTime)
+ - [[TUBEMQ-27](https://issues.apache.org/jira/browse/TUBEMQ-27)] replace StringBuffer with StringBuilder
+ - [[TUBEMQ-28](https://issues.apache.org/jira/browse/TUBEMQ-28)] ignore path error
+ - [[TUBEMQ-29](https://issues.apache.org/jira/browse/TUBEMQ-29)] Change the package name to org.apache.tubemq.""
+ - [[TUBEMQ-33](https://issues.apache.org/jira/browse/TUBEMQ-33)] refactor enum implement from annoymouse inner class
+ - [[TUBEMQ-38](https://issues.apache.org/jira/browse/TUBEMQ-38)] Correct DefaultLoadBalancer#balance parameter
+ - [[TUBEMQ-39](https://issues.apache.org/jira/browse/TUBEMQ-39)] Optimize the loadMessageStores() logic
+ - [[TUBEMQ-40](https://issues.apache.org/jira/browse/TUBEMQ-40)] Optimize message disk store classes's logic
+ - [[TUBEMQ-43](https://issues.apache.org/jira/browse/TUBEMQ-43)] Add DeletePolicy's value check
+ - [[TUBEMQ-44](https://issues.apache.org/jira/browse/TUBEMQ-44)] Remove unnecessary synchronized definition of shutdown () function
+ - [[TUBEMQ-49](https://issues.apache.org/jira/browse/TUBEMQ-49)] setTimeoutTime change to updTimeoutTime
+ - [[TUBEMQ-50](https://issues.apache.org/jira/browse/TUBEMQ-50)] Replace fastjson to gson
### Bug Fixes
- - [[inlong-10](https://issues.apache.org/jira/browse/inlong-10)] Fix Javadoc error
- - [[inlong-14](https://issues.apache.org/jira/browse/inlong-14)] Some compilation errors
- - [[inlong-15](https://issues.apache.org/jira/browse/inlong-15)] Correct typo in http_access_API_definition.md
- - [[inlong-32](https://issues.apache.org/jira/browse/inlong-32)] File path not match with package name in inlong-client module
- - [[inlong-35](https://issues.apache.org/jira/browse/inlong-35)] check illegal package's field value
- - [[inlong-36](https://issues.apache.org/jira/browse/inlong-36)] Remove unnecessary removefirst() function printing
- - [[inlong-37](https://issues.apache.org/jira/browse/inlong-37)] Offset is set to 0 when Broker goes offline
- - [[inlong-45](https://issues.apache.org/jira/browse/inlong-45)] Check groupName with checkHostName function
- - [[inlong-48](https://issues.apache.org/jira/browse/inlong-48)] No timeout when setting consumer timeout
- - [[inlong-59](https://issues.apache.org/jira/browse/inlong-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
- - [[inlong-62](https://issues.apache.org/jira/browse/inlong-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
- - [[inlong-66](https://issues.apache.org/jira/browse/inlong-66)] TubeSingleSessionFactory shutdown bug
- - [[inlong-85](https://issues.apache.org/jira/browse/inlong-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
- - [[inlong-88](https://issues.apache.org/jira/browse/inlong-88)] Broker does not take effect after the deletePolicy value is changed
- - [[inlong-149](https://issues.apache.org/jira/browse/inlong-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-153](https://issues.apache.org/jira/browse/inlong-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-10](https://issues.apache.org/jira/browse/TUBEMQ-10)] Fix Javadoc error
+ - [[TUBEMQ-14](https://issues.apache.org/jira/browse/TUBEMQ-14)] Some compilation errors
+ - [[TUBEMQ-15](https://issues.apache.org/jira/browse/TUBEMQ-15)] Correct typo in http_access_API_definition.md
+ - [[TUBEMQ-32](https://issues.apache.org/jira/browse/TUBEMQ-32)] File path not match with package name in tubemq-client module
+ - [[TUBEMQ-35](https://issues.apache.org/jira/browse/TUBEMQ-35)] check illegal package's field value
+ - [[TUBEMQ-36](https://issues.apache.org/jira/browse/TUBEMQ-36)] Remove unnecessary removefirst() function printing
+ - [[TUBEMQ-37](https://issues.apache.org/jira/browse/TUBEMQ-37)] Offset is set to 0 when Broker goes offline
+ - [[TUBEMQ-45](https://issues.apache.org/jira/browse/TUBEMQ-45)] Check groupName with checkHostName function
+ - [[TUBEMQ-48](https://issues.apache.org/jira/browse/TUBEMQ-48)] No timeout when setting consumer timeout
+ - [[TUBEMQ-59](https://issues.apache.org/jira/browse/TUBEMQ-59)] Null pointer exception is thrown while constructing ConsumerConfig with MasterInfo
+ - [[TUBEMQ-62](https://issues.apache.org/jira/browse/TUBEMQ-62)] consumed and set consumerConfig.setConsumeModel (0) for the first time
+ - [[TUBEMQ-66](https://issues.apache.org/jira/browse/TUBEMQ-66)] TubeSingleSessionFactory shutdown bug
+ - [[TUBEMQ-85](https://issues.apache.org/jira/browse/TUBEMQ-85)] There is NPE when creating PullConsumer with TubeSingleSessionFactory
+ - [[TUBEMQ-88](https://issues.apache.org/jira/browse/TUBEMQ-88)] Broker does not take effect after the deletePolicy value is changed
+ - [[TUBEMQ-149](https://issues.apache.org/jira/browse/TUBEMQ-149)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-153](https://issues.apache.org/jira/browse/TUBEMQ-153)] Some of the consumers stop consuming their corresponding partitions and never release the partition to others
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
diff --git a/en-us/docs/download/release-0.5.0.html b/en-us/docs/download/release-0.5.0.html
index aad9323..e194274 100644
--- a/en-us/docs/download/release-0.5.0.html
+++ b/en-us/docs/download/release-0.5.0.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="release-0.5.0" />
<meta name="description" content="release-0.5.0" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong from one of our mirrors.</p>
-<h2>inlong</h2>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>
+<h2>TubeMQ</h2>
<table>
<thead>
<tr>
@@ -29,111 +29,111 @@
<td style="text-align:center">August. 4th, 2020</td>
<td style="text-align:center">0.5.0</td>
<td style="text-align:center">Source</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Client</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Server</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
</tbody>
</table>
<h2>Release Notes</h2>
<h3>New Features</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-122">inlong-122</a>] Increase JAVA version collection of SDK environment</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-163">inlong-163</a>] Flume sink for inlong</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-197">inlong-197</a>] Support inlong connector for Apache Flink</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-238">inlong-238</a>] Support inlong connector for Apache Spark Streaming</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-239">inlong-239</a>] support deployment on kubernetes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-122">TUBEMQ-122</a>] Increase JAVA version collection of SDK environment</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-163">TUBEMQ-163</a>] Flume sink for TubeMQ</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-197">TUBEMQ-197</a>] Support TubeMQ connector for Apache Flink</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-238">TUBEMQ-238</a>] Support TubeMQ connector for Apache Spark Streaming</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-239">TUBEMQ-239</a>] support deployment on kubernetes</li>
</ul>
<h3>IMPROVEMENTS:</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-46">inlong-46</a>] Correct some spelling issues</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-53">inlong-53</a>] fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-55">inlong-55</a>] fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-57">inlong-57</a>] fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-58">inlong-58</a>] fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-60">inlong-60</a>] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-61">inlong-61</a>] minor update & fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-64">inlong-64</a>] minor update & fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-67">inlong-67</a>] remove synchronized & fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-71">inlong-71</a>] using IllegalArgumentException & fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-73">inlong-73</a>] remove duplicate codes & some minor updates</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-74">inlong-74</a>] minor updates for DefaultBdbStoreService</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-75">inlong-75</a>] remove unused Logger</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-76">inlong-76</a>] rename the classes</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-77">inlong-77</a>] fix typo</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-79">inlong-79</a>] fix typo</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-80">inlong-80</a>] Fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-82">inlong-82</a>] Fix some typos & update comments</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-83">inlong-83</a>] Fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-87">inlong-87</a>] Minor updates</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-89">inlong-89</a>] Minor updates</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-90">inlong-90</a>] Remove unused codes in TubeBroker</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-91">inlong-91</a>] replace explicit type with <></li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-93">inlong-93</a>] Substitute the parameterized type for client module & missed server module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-94">inlong-94</a>] Substitute the parameterized type for core module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-95">inlong-95</a>] Substitute the parameterized type for server module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-96">inlong-96</a>] Fix typo & use IllegalArgumentException</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-98">inlong-98</a>] Fix typo & Simplify 'instanceof' judgment</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-100">inlong-100</a>] Fix typos & remove unused codes</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-101">inlong-101</a>] Optimize code & Fix type</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-103">inlong-103</a>] Substitute Chinese comments with English</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-108">inlong-108</a>] About maven jdk version configuration problem</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-127">inlong-127</a>] Fixed a bug & minor changes</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-128">inlong-128</a>] Shorten the log clearup check cycle</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-138">inlong-138</a>] Optimize core module test case code</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-141">inlong-141</a>] Remove the requirement to provide localHostIP</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-152">inlong-152</a>] Modify the master.ini file's annotations</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-154">inlong-154</a>] Modify the wrong comment & Minor changes for example module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-155">inlong-155</a>] Use enum class for consume position</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-156">inlong-156</a>] Update for <a href="http://README.md">README.md</a></li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-166">inlong-166</a>] Hide <code>bdbStore</code> configs in master.ini</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-167">inlong-167</a>] Change to relative paths in default configs</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-168">inlong-168</a>] Example module: remove localhost IP configuration parameters</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-170">inlong-170</a>] improve build/deployment/configuration for quick start</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-196">inlong-196</a>] use log to print exception</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-201">inlong-201</a>] [Website] Adjust user guide & fix demo example</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-202">inlong-202</a>] Add protobuf protocol syntax declaration</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-213">inlong-213</a>] Optimize code & Minor changes</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-216">inlong-216</a>] use ThreadUtil.sleep replace Thread.sleep</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-222">inlong-222</a>] Optimize code: Unnecessary boxing/unboxing conversion</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-224">inlong-224</a>] Fixed: Unnecessary conversion to string inspection for server module</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-226">inlong-226</a>] Add Windows startup scripts</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-227">inlong-227</a>] remove build guide in docker-build readme</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-232">inlong-232</a>] TubeBroker#register2Master, reconnect and wait</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-234">inlong-234</a>] Add .asf.yaml to change notifications</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-235">inlong-235</a>] Add code coverage supporting for pull request created.</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-237">inlong-237</a>] add maven module build for docker image</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-46">TUBEMQ-46</a>] Correct some spelling issues</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-53">TUBEMQ-53</a>] fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-55">TUBEMQ-55</a>] fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-57">TUBEMQ-57</a>] fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-58">TUBEMQ-58</a>] fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-60">TUBEMQ-60</a>] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-61">TUBEMQ-61</a>] minor update & fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-64">TUBEMQ-64</a>] minor update & fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-67">TUBEMQ-67</a>] remove synchronized & fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-71">TUBEMQ-71</a>] using IllegalArgumentException & fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-73">TUBEMQ-73</a>] remove duplicate codes & some minor updates</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-74">TUBEMQ-74</a>] minor updates for DefaultBdbStoreService</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-75">TUBEMQ-75</a>] remove unused Logger</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-76">TUBEMQ-76</a>] rename the classes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-77">TUBEMQ-77</a>] fix typo</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-79">TUBEMQ-79</a>] fix typo</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-80">TUBEMQ-80</a>] Fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-82">TUBEMQ-82</a>] Fix some typos & update comments</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-83">TUBEMQ-83</a>] Fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-87">TUBEMQ-87</a>] Minor updates</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-89">TUBEMQ-89</a>] Minor updates</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-90">TUBEMQ-90</a>] Remove unused codes in TubeBroker</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-91">TUBEMQ-91</a>] replace explicit type with <></li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-93">TUBEMQ-93</a>] Substitute the parameterized type for client module & missed server module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-94">TUBEMQ-94</a>] Substitute the parameterized type for core module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-95">TUBEMQ-95</a>] Substitute the parameterized type for server module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-96">TUBEMQ-96</a>] Fix typo & use IllegalArgumentException</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-98">TUBEMQ-98</a>] Fix typo & Simplify 'instanceof' judgment</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-100">TUBEMQ-100</a>] Fix typos & remove unused codes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-101">TUBEMQ-101</a>] Optimize code & Fix type</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-103">TUBEMQ-103</a>] Substitute Chinese comments with English</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-108">TUBEMQ-108</a>] About maven jdk version configuration problem</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-127">TUBEMQ-127</a>] Fixed a bug & minor changes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-128">TUBEMQ-128</a>] Shorten the log clearup check cycle</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-138">TUBEMQ-138</a>] Optimize core module test case code</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-141">TUBEMQ-141</a>] Remove the requirement to provide localHostIP</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-152">TUBEMQ-152</a>] Modify the master.ini file's annotations</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-154">TUBEMQ-154</a>] Modify the wrong comment & Minor changes for example module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-155">TUBEMQ-155</a>] Use enum class for consume position</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-156">TUBEMQ-156</a>] Update for <a href="http://README.md">README.md</a></li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-166">TUBEMQ-166</a>] Hide <code>bdbStore</code> configs in master.ini</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-167">TUBEMQ-167</a>] Change to relative paths in default configs</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-168">TUBEMQ-168</a>] Example module: remove localhost IP configuration parameters</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-170">TUBEMQ-170</a>] improve build/deployment/configuration for quick start</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-196">TUBEMQ-196</a>] use log to print exception</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-201">TUBEMQ-201</a>] [Website] Adjust user guide & fix demo example</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-202">TUBEMQ-202</a>] Add protobuf protocol syntax declaration</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-213">TUBEMQ-213</a>] Optimize code & Minor changes</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-216">TUBEMQ-216</a>] use ThreadUtil.sleep replace Thread.sleep</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-222">TUBEMQ-222</a>] Optimize code: Unnecessary boxing/unboxing conversion</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-224">TUBEMQ-224</a>] Fixed: Unnecessary conversion to string inspection for server module</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-226">TUBEMQ-226</a>] Add Windows startup scripts</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-227">TUBEMQ-227</a>] remove build guide in docker-build readme</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-232">TUBEMQ-232</a>] TubeBroker#register2Master, reconnect and wait</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-234">TUBEMQ-234</a>] Add .asf.yaml to change notifications</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-235">TUBEMQ-235</a>] Add code coverage supporting for pull request created.</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-237">TUBEMQ-237</a>] add maven module build for docker image</li>
</ul>
<h3>BUG FIXES:</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-47">inlong-47</a>] Fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-102">inlong-102</a>] Fix question [inlong-101] [Optimize code]</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-121">inlong-121</a>] Fix compilation alarm</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-139">inlong-139</a>] a bug in the equals method of the TubeClientConfig class</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-157">inlong-157</a>] Optimize Broker disk anomaly check</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-158">inlong-158</a>] nextWithAuthInfo2B status should be managed independently according to Broker</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-159">inlong-159</a>] Fix some typos</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-165">inlong-165</a>] Remove unnecessary fiiles</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-205">inlong-205</a>] Duplicate dependency of jetty in tuber-server pom file</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-206">inlong-206</a>] There are some residual files after executed unit tests</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-210">inlong-210</a>] Add log4j properties file for unit tests</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-217">inlong-217</a>] UPdate the je download path</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-218">inlong-218</a>] build failed: Too many files with unapproved license</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-230">inlong-230</a>] inlong run mvn test failed with openjdk version 13.0.2</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-236">inlong-236</a>] Can't get dependencies from the maven repository</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-253">inlong-253</a>] tube-consumer fetch-worker cpu used too high</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-254">inlong-254</a>] support using different mapping port for standalone mode</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-265">inlong-265</a>] Unexpected broker disappearance in broker list after updating default broker metadata</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-47">TUBEMQ-47</a>] Fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-102">TUBEMQ-102</a>] Fix question [TUBEMQ-101] [Optimize code]</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-121">TUBEMQ-121</a>] Fix compilation alarm</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-139">TUBEMQ-139</a>] a bug in the equals method of the TubeClientConfig class</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-157">TUBEMQ-157</a>] Optimize Broker disk anomaly check</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-158">TUBEMQ-158</a>] nextWithAuthInfo2B status should be managed independently according to Broker</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-159">TUBEMQ-159</a>] Fix some typos</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-165">TUBEMQ-165</a>] Remove unnecessary fiiles</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-205">TUBEMQ-205</a>] Duplicate dependency of jetty in tuber-server pom file</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-206">TUBEMQ-206</a>] There are some residual files after executed unit tests</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-210">TUBEMQ-210</a>] Add log4j properties file for unit tests</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-217">TUBEMQ-217</a>] UPdate the je download path</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-218">TUBEMQ-218</a>] build failed: Too many files with unapproved license</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-230">TUBEMQ-230</a>] TubeMQ run mvn test failed with openjdk version 13.0.2</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-236">TUBEMQ-236</a>] Can't get dependencies from the maven repository</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-253">TUBEMQ-253</a>] tube-consumer fetch-worker cpu used too high</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-254">TUBEMQ-254</a>] support using different mapping port for standalone mode</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-265">TUBEMQ-265</a>] Unexpected broker disappearance in broker list after updating default broker metadata</li>
</ul>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
diff --git a/en-us/docs/download/release-0.5.0.json b/en-us/docs/download/release-0.5.0.json
index 336f7be..c5cd4fa 100644
--- a/en-us/docs/download/release-0.5.0.json
+++ b/en-us/docs/download/release-0.5.0.json
@@ -1,8 +1,8 @@
{
"filename": "release-0.5.0.md",
- "__html": "<h1>Download the inlong releases</h1>\n<p>Use the links below to download the Apache inlong from one of our mirrors.</p>\n<h2>inlong</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">August. 4th, 2020</td>\n<td style=\"text-align:center\">0.5.0</td>\n< [...]
+ "__html": "<h1>Download the TubeMQ releases</h1>\n<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>\n<h2>TubeMQ</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">August. 4th, 2020</td>\n<td style=\"text-align:center\">0.5.0</td>\n< [...]
"link": "/en-us/docs/download/release-0.5.0.html",
"meta": {
- "title": "Download - Apache inlong"
+ "title": "Download - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.5.0.md b/en-us/docs/download/release-0.5.0.md
index a732263..e6c4ef1 100644
--- a/en-us/docs/download/release-0.5.0.md
+++ b/en-us/docs/download/release-0.5.0.md
@@ -1,104 +1,104 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| August. 4th, 2020 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-0.5.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-client-0.5.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.5.0-incubating/apache-inlong-server-0.5.0-incubating-bin.tar.gz.sha512)] |
+| August. 4th, 2020 | 0.5.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-0.5.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-client-0.5.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.5.0-incubating/apache-tubemq-server-0.5.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
- - [[inlong-122](https://issues.apache.org/jira/browse/inlong-122)] Increase JAVA version collection of SDK environment
- - [[inlong-163](https://issues.apache.org/jira/browse/inlong-163)] Flume sink for inlong
- - [[inlong-197](https://issues.apache.org/jira/browse/inlong-197)] Support inlong connector for Apache Flink
- - [[inlong-238](https://issues.apache.org/jira/browse/inlong-238)] Support inlong connector for Apache Spark Streaming
- - [[inlong-239](https://issues.apache.org/jira/browse/inlong-239)] support deployment on kubernetes
+ - [[TUBEMQ-122](https://issues.apache.org/jira/browse/TUBEMQ-122)] Increase JAVA version collection of SDK environment
+ - [[TUBEMQ-163](https://issues.apache.org/jira/browse/TUBEMQ-163)] Flume sink for TubeMQ
+ - [[TUBEMQ-197](https://issues.apache.org/jira/browse/TUBEMQ-197)] Support TubeMQ connector for Apache Flink
+ - [[TUBEMQ-238](https://issues.apache.org/jira/browse/TUBEMQ-238)] Support TubeMQ connector for Apache Spark Streaming
+ - [[TUBEMQ-239](https://issues.apache.org/jira/browse/TUBEMQ-239)] support deployment on kubernetes
### IMPROVEMENTS:
- - [[inlong-46](https://issues.apache.org/jira/browse/inlong-46)] Correct some spelling issues
- - [[inlong-53](https://issues.apache.org/jira/browse/inlong-53)] fix some typos
- - [[inlong-55](https://issues.apache.org/jira/browse/inlong-55)] fix some typos
- - [[inlong-57](https://issues.apache.org/jira/browse/inlong-57)] fix some typos
- - [[inlong-58](https://issues.apache.org/jira/browse/inlong-58)] fix some typos
- - [[inlong-60](https://issues.apache.org/jira/browse/inlong-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
- - [[inlong-61](https://issues.apache.org/jira/browse/inlong-61)] minor update & fix some typos
- - [[inlong-64](https://issues.apache.org/jira/browse/inlong-64)] minor update & fix some typos
- - [[inlong-67](https://issues.apache.org/jira/browse/inlong-67)] remove synchronized & fix some typos
- - [[inlong-71](https://issues.apache.org/jira/browse/inlong-71)] using IllegalArgumentException & fix some typos
- - [[inlong-73](https://issues.apache.org/jira/browse/inlong-73)] remove duplicate codes & some minor updates
- - [[inlong-74](https://issues.apache.org/jira/browse/inlong-74)] minor updates for DefaultBdbStoreService
- - [[inlong-75](https://issues.apache.org/jira/browse/inlong-75)] remove unused Logger
- - [[inlong-76](https://issues.apache.org/jira/browse/inlong-76)] rename the classes
- - [[inlong-77](https://issues.apache.org/jira/browse/inlong-77)] fix typo
- - [[inlong-79](https://issues.apache.org/jira/browse/inlong-79)] fix typo
- - [[inlong-80](https://issues.apache.org/jira/browse/inlong-80)] Fix some typos
- - [[inlong-82](https://issues.apache.org/jira/browse/inlong-82)] Fix some typos & update comments
- - [[inlong-83](https://issues.apache.org/jira/browse/inlong-83)] Fix some typos
- - [[inlong-87](https://issues.apache.org/jira/browse/inlong-87)] Minor updates
- - [[inlong-89](https://issues.apache.org/jira/browse/inlong-89)] Minor updates
- - [[inlong-90](https://issues.apache.org/jira/browse/inlong-90)] Remove unused codes in TubeBroker
- - [[inlong-91](https://issues.apache.org/jira/browse/inlong-91)] replace explicit type with <>
- - [[inlong-93](https://issues.apache.org/jira/browse/inlong-93)] Substitute the parameterized type for client module & missed server module
- - [[inlong-94](https://issues.apache.org/jira/browse/inlong-94)] Substitute the parameterized type for core module
- - [[inlong-95](https://issues.apache.org/jira/browse/inlong-95)] Substitute the parameterized type for server module
- - [[inlong-96](https://issues.apache.org/jira/browse/inlong-96)] Fix typo & use IllegalArgumentException
- - [[inlong-98](https://issues.apache.org/jira/browse/inlong-98)] Fix typo & Simplify 'instanceof' judgment
- - [[inlong-100](https://issues.apache.org/jira/browse/inlong-100)] Fix typos & remove unused codes
- - [[inlong-101](https://issues.apache.org/jira/browse/inlong-101)] Optimize code & Fix type
- - [[inlong-103](https://issues.apache.org/jira/browse/inlong-103)] Substitute Chinese comments with English
- - [[inlong-108](https://issues.apache.org/jira/browse/inlong-108)] About maven jdk version configuration problem
- - [[inlong-127](https://issues.apache.org/jira/browse/inlong-127)] Fixed a bug & minor changes
- - [[inlong-128](https://issues.apache.org/jira/browse/inlong-128)] Shorten the log clearup check cycle
- - [[inlong-138](https://issues.apache.org/jira/browse/inlong-138)] Optimize core module test case code
- - [[inlong-141](https://issues.apache.org/jira/browse/inlong-141)] Remove the requirement to provide localHostIP
- - [[inlong-152](https://issues.apache.org/jira/browse/inlong-152)] Modify the master.ini file's annotations
- - [[inlong-154](https://issues.apache.org/jira/browse/inlong-154)] Modify the wrong comment & Minor changes for example module
- - [[inlong-155](https://issues.apache.org/jira/browse/inlong-155)] Use enum class for consume position
- - [[inlong-156](https://issues.apache.org/jira/browse/inlong-156)] Update for README.md
- - [[inlong-166](https://issues.apache.org/jira/browse/inlong-166)] Hide `bdbStore` configs in master.ini
- - [[inlong-167](https://issues.apache.org/jira/browse/inlong-167)] Change to relative paths in default configs
- - [[inlong-168](https://issues.apache.org/jira/browse/inlong-168)] Example module: remove localhost IP configuration parameters
- - [[inlong-170](https://issues.apache.org/jira/browse/inlong-170)] improve build/deployment/configuration for quick start
- - [[inlong-196](https://issues.apache.org/jira/browse/inlong-196)] use log to print exception
- - [[inlong-201](https://issues.apache.org/jira/browse/inlong-201)] [Website] Adjust user guide & fix demo example
- - [[inlong-202](https://issues.apache.org/jira/browse/inlong-202)] Add protobuf protocol syntax declaration
- - [[inlong-213](https://issues.apache.org/jira/browse/inlong-213)] Optimize code & Minor changes
- - [[inlong-216](https://issues.apache.org/jira/browse/inlong-216)] use ThreadUtil.sleep replace Thread.sleep
- - [[inlong-222](https://issues.apache.org/jira/browse/inlong-222)] Optimize code: Unnecessary boxing/unboxing conversion
- - [[inlong-224](https://issues.apache.org/jira/browse/inlong-224)] Fixed: Unnecessary conversion to string inspection for server module
- - [[inlong-226](https://issues.apache.org/jira/browse/inlong-226)] Add Windows startup scripts
- - [[inlong-227](https://issues.apache.org/jira/browse/inlong-227)] remove build guide in docker-build readme
- - [[inlong-232](https://issues.apache.org/jira/browse/inlong-232)] TubeBroker#register2Master, reconnect and wait
- - [[inlong-234](https://issues.apache.org/jira/browse/inlong-234)] Add .asf.yaml to change notifications
- - [[inlong-235](https://issues.apache.org/jira/browse/inlong-235)] Add code coverage supporting for pull request created.
- - [[inlong-237](https://issues.apache.org/jira/browse/inlong-237)] add maven module build for docker image
+ - [[TUBEMQ-46](https://issues.apache.org/jira/browse/TUBEMQ-46)] Correct some spelling issues
+ - [[TUBEMQ-53](https://issues.apache.org/jira/browse/TUBEMQ-53)] fix some typos
+ - [[TUBEMQ-55](https://issues.apache.org/jira/browse/TUBEMQ-55)] fix some typos
+ - [[TUBEMQ-57](https://issues.apache.org/jira/browse/TUBEMQ-57)] fix some typos
+ - [[TUBEMQ-58](https://issues.apache.org/jira/browse/TUBEMQ-58)] fix some typos
+ - [[TUBEMQ-60](https://issues.apache.org/jira/browse/TUBEMQ-60)] Remove unnecessary synchronized & using IllegalArgumentException instead of IllegalStateException
+ - [[TUBEMQ-61](https://issues.apache.org/jira/browse/TUBEMQ-61)] minor update & fix some typos
+ - [[TUBEMQ-64](https://issues.apache.org/jira/browse/TUBEMQ-64)] minor update & fix some typos
+ - [[TUBEMQ-67](https://issues.apache.org/jira/browse/TUBEMQ-67)] remove synchronized & fix some typos
+ - [[TUBEMQ-71](https://issues.apache.org/jira/browse/TUBEMQ-71)] using IllegalArgumentException & fix some typos
+ - [[TUBEMQ-73](https://issues.apache.org/jira/browse/TUBEMQ-73)] remove duplicate codes & some minor updates
+ - [[TUBEMQ-74](https://issues.apache.org/jira/browse/TUBEMQ-74)] minor updates for DefaultBdbStoreService
+ - [[TUBEMQ-75](https://issues.apache.org/jira/browse/TUBEMQ-75)] remove unused Logger
+ - [[TUBEMQ-76](https://issues.apache.org/jira/browse/TUBEMQ-76)] rename the classes
+ - [[TUBEMQ-77](https://issues.apache.org/jira/browse/TUBEMQ-77)] fix typo
+ - [[TUBEMQ-79](https://issues.apache.org/jira/browse/TUBEMQ-79)] fix typo
+ - [[TUBEMQ-80](https://issues.apache.org/jira/browse/TUBEMQ-80)] Fix some typos
+ - [[TUBEMQ-82](https://issues.apache.org/jira/browse/TUBEMQ-82)] Fix some typos & update comments
+ - [[TUBEMQ-83](https://issues.apache.org/jira/browse/TUBEMQ-83)] Fix some typos
+ - [[TUBEMQ-87](https://issues.apache.org/jira/browse/TUBEMQ-87)] Minor updates
+ - [[TUBEMQ-89](https://issues.apache.org/jira/browse/TUBEMQ-89)] Minor updates
+ - [[TUBEMQ-90](https://issues.apache.org/jira/browse/TUBEMQ-90)] Remove unused codes in TubeBroker
+ - [[TUBEMQ-91](https://issues.apache.org/jira/browse/TUBEMQ-91)] replace explicit type with <>
+ - [[TUBEMQ-93](https://issues.apache.org/jira/browse/TUBEMQ-93)] Substitute the parameterized type for client module & missed server module
+ - [[TUBEMQ-94](https://issues.apache.org/jira/browse/TUBEMQ-94)] Substitute the parameterized type for core module
+ - [[TUBEMQ-95](https://issues.apache.org/jira/browse/TUBEMQ-95)] Substitute the parameterized type for server module
+ - [[TUBEMQ-96](https://issues.apache.org/jira/browse/TUBEMQ-96)] Fix typo & use IllegalArgumentException
+ - [[TUBEMQ-98](https://issues.apache.org/jira/browse/TUBEMQ-98)] Fix typo & Simplify 'instanceof' judgment
+ - [[TUBEMQ-100](https://issues.apache.org/jira/browse/TUBEMQ-100)] Fix typos & remove unused codes
+ - [[TUBEMQ-101](https://issues.apache.org/jira/browse/TUBEMQ-101)] Optimize code & Fix type
+ - [[TUBEMQ-103](https://issues.apache.org/jira/browse/TUBEMQ-103)] Substitute Chinese comments with English
+ - [[TUBEMQ-108](https://issues.apache.org/jira/browse/TUBEMQ-108)] About maven jdk version configuration problem
+ - [[TUBEMQ-127](https://issues.apache.org/jira/browse/TUBEMQ-127)] Fixed a bug & minor changes
+ - [[TUBEMQ-128](https://issues.apache.org/jira/browse/TUBEMQ-128)] Shorten the log clearup check cycle
+ - [[TUBEMQ-138](https://issues.apache.org/jira/browse/TUBEMQ-138)] Optimize core module test case code
+ - [[TUBEMQ-141](https://issues.apache.org/jira/browse/TUBEMQ-141)] Remove the requirement to provide localHostIP
+ - [[TUBEMQ-152](https://issues.apache.org/jira/browse/TUBEMQ-152)] Modify the master.ini file's annotations
+ - [[TUBEMQ-154](https://issues.apache.org/jira/browse/TUBEMQ-154)] Modify the wrong comment & Minor changes for example module
+ - [[TUBEMQ-155](https://issues.apache.org/jira/browse/TUBEMQ-155)] Use enum class for consume position
+ - [[TUBEMQ-156](https://issues.apache.org/jira/browse/TUBEMQ-156)] Update for README.md
+ - [[TUBEMQ-166](https://issues.apache.org/jira/browse/TUBEMQ-166)] Hide `bdbStore` configs in master.ini
+ - [[TUBEMQ-167](https://issues.apache.org/jira/browse/TUBEMQ-167)] Change to relative paths in default configs
+ - [[TUBEMQ-168](https://issues.apache.org/jira/browse/TUBEMQ-168)] Example module: remove localhost IP configuration parameters
+ - [[TUBEMQ-170](https://issues.apache.org/jira/browse/TUBEMQ-170)] improve build/deployment/configuration for quick start
+ - [[TUBEMQ-196](https://issues.apache.org/jira/browse/TUBEMQ-196)] use log to print exception
+ - [[TUBEMQ-201](https://issues.apache.org/jira/browse/TUBEMQ-201)] [Website] Adjust user guide & fix demo example
+ - [[TUBEMQ-202](https://issues.apache.org/jira/browse/TUBEMQ-202)] Add protobuf protocol syntax declaration
+ - [[TUBEMQ-213](https://issues.apache.org/jira/browse/TUBEMQ-213)] Optimize code & Minor changes
+ - [[TUBEMQ-216](https://issues.apache.org/jira/browse/TUBEMQ-216)] use ThreadUtil.sleep replace Thread.sleep
+ - [[TUBEMQ-222](https://issues.apache.org/jira/browse/TUBEMQ-222)] Optimize code: Unnecessary boxing/unboxing conversion
+ - [[TUBEMQ-224](https://issues.apache.org/jira/browse/TUBEMQ-224)] Fixed: Unnecessary conversion to string inspection for server module
+ - [[TUBEMQ-226](https://issues.apache.org/jira/browse/TUBEMQ-226)] Add Windows startup scripts
+ - [[TUBEMQ-227](https://issues.apache.org/jira/browse/TUBEMQ-227)] remove build guide in docker-build readme
+ - [[TUBEMQ-232](https://issues.apache.org/jira/browse/TUBEMQ-232)] TubeBroker#register2Master, reconnect and wait
+ - [[TUBEMQ-234](https://issues.apache.org/jira/browse/TUBEMQ-234)] Add .asf.yaml to change notifications
+ - [[TUBEMQ-235](https://issues.apache.org/jira/browse/TUBEMQ-235)] Add code coverage supporting for pull request created.
+ - [[TUBEMQ-237](https://issues.apache.org/jira/browse/TUBEMQ-237)] add maven module build for docker image
### BUG FIXES:
- - [[inlong-47](https://issues.apache.org/jira/browse/inlong-47)] Fix some typos
- - [[inlong-102](https://issues.apache.org/jira/browse/inlong-102)] Fix question [inlong-101] [Optimize code]
- - [[inlong-121](https://issues.apache.org/jira/browse/inlong-121)] Fix compilation alarm
- - [[inlong-139](https://issues.apache.org/jira/browse/inlong-139)] a bug in the equals method of the TubeClientConfig class
- - [[inlong-157](https://issues.apache.org/jira/browse/inlong-157)] Optimize Broker disk anomaly check
- - [[inlong-158](https://issues.apache.org/jira/browse/inlong-158)] nextWithAuthInfo2B status should be managed independently according to Broker
- - [[inlong-159](https://issues.apache.org/jira/browse/inlong-159)] Fix some typos
- - [[inlong-165](https://issues.apache.org/jira/browse/inlong-165)] Remove unnecessary fiiles
- - [[inlong-205](https://issues.apache.org/jira/browse/inlong-205)] Duplicate dependency of jetty in tuber-server pom file
- - [[inlong-206](https://issues.apache.org/jira/browse/inlong-206)] There are some residual files after executed unit tests
- - [[inlong-210](https://issues.apache.org/jira/browse/inlong-210)] Add log4j properties file for unit tests
- - [[inlong-217](https://issues.apache.org/jira/browse/inlong-217)] UPdate the je download path
- - [[inlong-218](https://issues.apache.org/jira/browse/inlong-218)] build failed: Too many files with unapproved license
- - [[inlong-230](https://issues.apache.org/jira/browse/inlong-230)] inlong run mvn test failed with openjdk version 13.0.2
- - [[inlong-236](https://issues.apache.org/jira/browse/inlong-236)] Can't get dependencies from the maven repository
- - [[inlong-253](https://issues.apache.org/jira/browse/inlong-253)] tube-consumer fetch-worker cpu used too high
- - [[inlong-254](https://issues.apache.org/jira/browse/inlong-254)] support using different mapping port for standalone mode
- - [[inlong-265](https://issues.apache.org/jira/browse/inlong-265)] Unexpected broker disappearance in broker list after updating default broker metadata
+ - [[TUBEMQ-47](https://issues.apache.org/jira/browse/TUBEMQ-47)] Fix some typos
+ - [[TUBEMQ-102](https://issues.apache.org/jira/browse/TUBEMQ-102)] Fix question [TUBEMQ-101] [Optimize code]
+ - [[TUBEMQ-121](https://issues.apache.org/jira/browse/TUBEMQ-121)] Fix compilation alarm
+ - [[TUBEMQ-139](https://issues.apache.org/jira/browse/TUBEMQ-139)] a bug in the equals method of the TubeClientConfig class
+ - [[TUBEMQ-157](https://issues.apache.org/jira/browse/TUBEMQ-157)] Optimize Broker disk anomaly check
+ - [[TUBEMQ-158](https://issues.apache.org/jira/browse/TUBEMQ-158)] nextWithAuthInfo2B status should be managed independently according to Broker
+ - [[TUBEMQ-159](https://issues.apache.org/jira/browse/TUBEMQ-159)] Fix some typos
+ - [[TUBEMQ-165](https://issues.apache.org/jira/browse/TUBEMQ-165)] Remove unnecessary fiiles
+ - [[TUBEMQ-205](https://issues.apache.org/jira/browse/TUBEMQ-205)] Duplicate dependency of jetty in tuber-server pom file
+ - [[TUBEMQ-206](https://issues.apache.org/jira/browse/TUBEMQ-206)] There are some residual files after executed unit tests
+ - [[TUBEMQ-210](https://issues.apache.org/jira/browse/TUBEMQ-210)] Add log4j properties file for unit tests
+ - [[TUBEMQ-217](https://issues.apache.org/jira/browse/TUBEMQ-217)] UPdate the je download path
+ - [[TUBEMQ-218](https://issues.apache.org/jira/browse/TUBEMQ-218)] build failed: Too many files with unapproved license
+ - [[TUBEMQ-230](https://issues.apache.org/jira/browse/TUBEMQ-230)] TubeMQ run mvn test failed with openjdk version 13.0.2
+ - [[TUBEMQ-236](https://issues.apache.org/jira/browse/TUBEMQ-236)] Can't get dependencies from the maven repository
+ - [[TUBEMQ-253](https://issues.apache.org/jira/browse/TUBEMQ-253)] tube-consumer fetch-worker cpu used too high
+ - [[TUBEMQ-254](https://issues.apache.org/jira/browse/TUBEMQ-254)] support using different mapping port for standalone mode
+ - [[TUBEMQ-265](https://issues.apache.org/jira/browse/TUBEMQ-265)] Unexpected broker disappearance in broker list after updating default broker metadata
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.6.0.html b/en-us/docs/download/release-0.6.0.html
index 9076ba7..de30ba2 100644
--- a/en-us/docs/download/release-0.6.0.html
+++ b/en-us/docs/download/release-0.6.0.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="release-0.6.0" />
<meta name="description" content="release-0.6.0" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong from one of our mirrors.</p>
-<h2>inlong</h2>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>
+<h2>TubeMQ</h2>
<table>
<thead>
<tr>
@@ -29,47 +29,47 @@
<td style="text-align:center">October. 21th, 2020</td>
<td style="text-align:center">0.6.0</td>
<td style="text-align:center">Source</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Client</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Server</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
</tbody>
</table>
<h2>Release Notes</h2>
<h3>New Features</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-319">inlong-319</a>] In the pull mode, consumers support the suspension of consumption for a certain partition</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-3">inlong-3</a>] C++ SDK support in inlong</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-319">TUBEMQ-319</a>] In the pull mode, consumers support the suspension of consumption for a certain partition</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-3">TUBEMQ-3</a>] C++ SDK support in TubeMQ</li>
</ul>
<h3>IMPROVEMENTS</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-311">inlong-311</a>] Feedback more production information</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-312">inlong-312</a>] Feedback more consumption information</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-325">inlong-325</a>] Add 406 ~ 408 error code to pullSelect call</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-345">inlong-345</a>] Optimize the call logic of getMessage() in Pull mode</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-352">inlong-352</a>] Set the parameters of the example at startup</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-353">inlong-353</a>] Update LICENSE about C/C++ SDK's code reference</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-356">inlong-356</a>] C++ SDK Codec decode add requestid</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-327">inlong-327</a>] Fix the concurrency problem in the example</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-311">TUBEMQ-311</a>] Feedback more production information</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-312">TUBEMQ-312</a>] Feedback more consumption information</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-325">TUBEMQ-325</a>] Add 406 ~ 408 error code to pullSelect call</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-345">TUBEMQ-345</a>] Optimize the call logic of getMessage() in Pull mode</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-352">TUBEMQ-352</a>] Set the parameters of the example at startup</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-353">TUBEMQ-353</a>] Update LICENSE about C/C++ SDK's code reference</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-356">TUBEMQ-356</a>] C++ SDK Codec decode add requestid</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-327">TUBEMQ-327</a>] Fix the concurrency problem in the example</li>
</ul>
<h3>BUG FIXES</h3>
<ul>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-316">inlong-316</a>] Where the port the port is aleady used, the process throw the exception, but not exit</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-317">inlong-317</a>] The Store Manager throws java.lang.NullPointerException</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-320">inlong-320</a>] Request for static web contents would get responses with no content</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-354">inlong-354</a>] Found a dns translate bug in C/C++ sdk</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-306">inlong-306</a>] Raise Nullpointer Exception when create inlong instance</li>
-<li>[<a href="https://issues.apache.org/jira/browse/inlong-359">inlong-359</a>] inlong consume speed dropped to 0 in some partitions, it is a very serious bug Blocker</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-316">TUBEMQ-316</a>] Where the port the port is aleady used, the process throw the exception, but not exit</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-317">TUBEMQ-317</a>] The Store Manager throws java.lang.NullPointerException</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-320">TUBEMQ-320</a>] Request for static web contents would get responses with no content</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-354">TUBEMQ-354</a>] Found a dns translate bug in C/C++ sdk</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-306">TUBEMQ-306</a>] Raise Nullpointer Exception when create tubemq instance</li>
+<li>[<a href="https://issues.apache.org/jira/browse/TUBEMQ-359">TUBEMQ-359</a>] TubeMQ consume speed dropped to 0 in some partitions, it is a very serious bug Blocker</li>
</ul>
</div></section><footer class="footer-container"><div class="footer-body"><img src="/img/incubator-logo.svg"/><div class="cols-container"><div class="col col-24"><p>Apache InLong (incubating) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by Incubator. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with [...]
<script src="https://f.alicdn.com/react/15.4.1/react-with-addons.min.js"></script>
diff --git a/en-us/docs/download/release-0.6.0.json b/en-us/docs/download/release-0.6.0.json
index 526d51b..8a3c961 100644
--- a/en-us/docs/download/release-0.6.0.json
+++ b/en-us/docs/download/release-0.6.0.json
@@ -1,8 +1,8 @@
{
"filename": "release-0.6.0.md",
- "__html": "<h1>Download the inlong releases</h1>\n<p>Use the links below to download the Apache inlong from one of our mirrors.</p>\n<h2>inlong</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">October. 21th, 2020</td>\n<td style=\"text-align:center\">0.6.0</td>\ [...]
+ "__html": "<h1>Download the TubeMQ releases</h1>\n<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>\n<h2>TubeMQ</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">October. 21th, 2020</td>\n<td style=\"text-align:center\">0.6.0</td>\ [...]
"link": "/en-us/docs/download/release-0.6.0.html",
"meta": {
- "title": "Download - Apache inlong"
+ "title": "Download - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.6.0.md b/en-us/docs/download/release-0.6.0.md
index 77efdf4..e171aa7 100644
--- a/en-us/docs/download/release-0.6.0.md
+++ b/en-us/docs/download/release-0.6.0.md
@@ -1,39 +1,39 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| October. 21th, 2020 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-0.6.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-client-0.6.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.6.0-incubating/apache-inlong-server-0.6.0-incubating-bin.tar.gz.sha512)] |
+| October. 21th, 2020 | 0.6.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-0.6.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-client-0.6.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.6.0-incubating/apache-tubemq-server-0.6.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
### New Features
-- [[inlong-319](https://issues.apache.org/jira/browse/inlong-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
-- [[inlong-3](https://issues.apache.org/jira/browse/inlong-3)] C++ SDK support in inlong
+- [[TUBEMQ-319](https://issues.apache.org/jira/browse/TUBEMQ-319)] In the pull mode, consumers support the suspension of consumption for a certain partition
+- [[TUBEMQ-3](https://issues.apache.org/jira/browse/TUBEMQ-3)] C++ SDK support in TubeMQ
### IMPROVEMENTS
-- [[inlong-311](https://issues.apache.org/jira/browse/inlong-311)] Feedback more production information
-- [[inlong-312](https://issues.apache.org/jira/browse/inlong-312)] Feedback more consumption information
-- [[inlong-325](https://issues.apache.org/jira/browse/inlong-325)] Add 406 ~ 408 error code to pullSelect call
-- [[inlong-345](https://issues.apache.org/jira/browse/inlong-345)] Optimize the call logic of getMessage() in Pull mode
-- [[inlong-352](https://issues.apache.org/jira/browse/inlong-352)] Set the parameters of the example at startup
-- [[inlong-353](https://issues.apache.org/jira/browse/inlong-353)] Update LICENSE about C/C++ SDK's code reference
-- [[inlong-356](https://issues.apache.org/jira/browse/inlong-356)] C++ SDK Codec decode add requestid
-- [[inlong-327](https://issues.apache.org/jira/browse/inlong-327)] Fix the concurrency problem in the example
+- [[TUBEMQ-311](https://issues.apache.org/jira/browse/TUBEMQ-311)] Feedback more production information
+- [[TUBEMQ-312](https://issues.apache.org/jira/browse/TUBEMQ-312)] Feedback more consumption information
+- [[TUBEMQ-325](https://issues.apache.org/jira/browse/TUBEMQ-325)] Add 406 ~ 408 error code to pullSelect call
+- [[TUBEMQ-345](https://issues.apache.org/jira/browse/TUBEMQ-345)] Optimize the call logic of getMessage() in Pull mode
+- [[TUBEMQ-352](https://issues.apache.org/jira/browse/TUBEMQ-352)] Set the parameters of the example at startup
+- [[TUBEMQ-353](https://issues.apache.org/jira/browse/TUBEMQ-353)] Update LICENSE about C/C++ SDK's code reference
+- [[TUBEMQ-356](https://issues.apache.org/jira/browse/TUBEMQ-356)] C++ SDK Codec decode add requestid
+- [[TUBEMQ-327](https://issues.apache.org/jira/browse/TUBEMQ-327)] Fix the concurrency problem in the example
### BUG FIXES
-- [[inlong-316](https://issues.apache.org/jira/browse/inlong-316)] Where the port the port is aleady used, the process throw the exception, but not exit
-- [[inlong-317](https://issues.apache.org/jira/browse/inlong-317)] The Store Manager throws java.lang.NullPointerException
-- [[inlong-320](https://issues.apache.org/jira/browse/inlong-320)] Request for static web contents would get responses with no content
-- [[inlong-354](https://issues.apache.org/jira/browse/inlong-354)] Found a dns translate bug in C/C++ sdk
-- [[inlong-306](https://issues.apache.org/jira/browse/inlong-306)] Raise Nullpointer Exception when create inlong instance
-- [[inlong-359](https://issues.apache.org/jira/browse/inlong-359)] inlong consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
+- [[TUBEMQ-316](https://issues.apache.org/jira/browse/TUBEMQ-316)] Where the port the port is aleady used, the process throw the exception, but not exit
+- [[TUBEMQ-317](https://issues.apache.org/jira/browse/TUBEMQ-317)] The Store Manager throws java.lang.NullPointerException
+- [[TUBEMQ-320](https://issues.apache.org/jira/browse/TUBEMQ-320)] Request for static web contents would get responses with no content
+- [[TUBEMQ-354](https://issues.apache.org/jira/browse/TUBEMQ-354)] Found a dns translate bug in C/C++ sdk
+- [[TUBEMQ-306](https://issues.apache.org/jira/browse/TUBEMQ-306)] Raise Nullpointer Exception when create tubemq instance
+- [[TUBEMQ-359](https://issues.apache.org/jira/browse/TUBEMQ-359)] TubeMQ consume speed dropped to 0 in some partitions, it is a very serious bug Blocker
diff --git a/en-us/docs/download/release-0.7.0.html b/en-us/docs/download/release-0.7.0.html
index 5c465af..2a80cc1 100644
--- a/en-us/docs/download/release-0.7.0.html
+++ b/en-us/docs/download/release-0.7.0.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="release-0.7.0" />
<meta name="description" content="release-0.7.0" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong from one of our mirrors.</p>
-<h2>inlong</h2>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>
+<h2>TubeMQ</h2>
<table>
<thead>
<tr>
@@ -29,19 +29,19 @@
<td style="text-align:center">December. 4th, 2020</td>
<td style="text-align:center">0.7.0</td>
<td style="text-align:center">Source</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Client</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Server</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
</tbody>
</table>
@@ -57,17 +57,17 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-162">inlong-162</a></td>
-<td style="text-align:left">Python SDK support in inlong</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-162">TUBEMQ-162</a></td>
+<td style="text-align:left">Python SDK support in TubeMQ</td>
<td style="text-align:left">High</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-336">inlong-336</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-336">TUBEMQ-336</a></td>
<td style="text-align:left">Propose web portal to manage tube cluster Phase-I</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-390">inlong-390</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-390">TUBEMQ-390</a></td>
<td style="text-align:left">support build C++ SDK with docker image</td>
<td style="text-align:left">Normal</td>
</tr>
@@ -84,57 +84,57 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-369">inlong-369</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-369">TUBEMQ-369</a></td>
<td style="text-align:left">hope to add an option in the compilation script (like <code>make lib</code> etc...)</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-373">inlong-373</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-373">TUBEMQ-373</a></td>
<td style="text-align:left">Reduce the redundant code of Utils::Split functions</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-374">inlong-374</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-374">TUBEMQ-374</a></td>
<td style="text-align:left">Adjust some coding style issues</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-375">inlong-375</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-375">TUBEMQ-375</a></td>
<td style="text-align:left">Add a section to the README file about how to compile the project</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-385">inlong-385</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-385">TUBEMQ-385</a></td>
<td style="text-align:left">update docker images</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-393">inlong-393</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-393">TUBEMQ-393</a></td>
<td style="text-align:left">Optimize the mapping code of WEB API</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-406">inlong-406</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-406">TUBEMQ-406</a></td>
<td style="text-align:left">test_consumer.py works for both Python 2 and 3</td>
<td style="text-align:left">Minor</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-410">inlong-410</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-410">TUBEMQ-410</a></td>
<td style="text-align:left">install python package and simplify test_consumer.py</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-416">inlong-416</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-416">TUBEMQ-416</a></td>
<td style="text-align:left">support consume from specified position</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-417">inlong-417</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-417">TUBEMQ-417</a></td>
<td style="text-align:left">C++ Client support parse message from binary data for Python SDK</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-419">inlong-419</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-419">TUBEMQ-419</a></td>
<td style="text-align:left">SetMaxPartCheckPeriodMs() negative number, getMessage() still</td>
<td style="text-align:left">Major</td>
</tr>
@@ -151,52 +151,52 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-365">inlong-365</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-365">TUBEMQ-365</a></td>
<td style="text-align:left">Whether the consumption setting is wrong after the processRequest exception</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-370">inlong-370</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-370">TUBEMQ-370</a></td>
<td style="text-align:left">Calling GetCurConsumedInfo API always returns failure</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-376">inlong-376</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-376">TUBEMQ-376</a></td>
<td style="text-align:left">Move pullrequests_status notifications commits mail list</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-366">inlong-366</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-366">TUBEMQ-366</a></td>
<td style="text-align:left">Found a nullpointerexception bug in broker</td>
<td style="text-align:left">Normal</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-379">inlong-379</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-379">TUBEMQ-379</a></td>
<td style="text-align:left">Modify the memory cache size default to 3M</td>
<td style="text-align:left">Normal</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-380">inlong-380</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-380">TUBEMQ-380</a></td>
<td style="text-align:left">Cpp client link error when gcc optimization is disabled</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-405">inlong-405</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-405">TUBEMQ-405</a></td>
<td style="text-align:left">python sdk install files lack of the whole cpp configuration</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-401">inlong-401</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-401">TUBEMQ-401</a></td>
<td style="text-align:left">python sdk readme bug</td>
<td style="text-align:left">Minor</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-407">inlong-407</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-407">TUBEMQ-407</a></td>
<td style="text-align:left">Fix some content in <a href="http://README.md">README.md</a></td>
<td style="text-align:left">Trivial</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-418">inlong-418</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-418">TUBEMQ-418</a></td>
<td style="text-align:left">C++ SDK function SetMaxPartCheckPeriodMs() can't work</td>
<td style="text-align:left">Major</td>
</tr>
diff --git a/en-us/docs/download/release-0.7.0.json b/en-us/docs/download/release-0.7.0.json
index bb7d360..8a9b767 100644
--- a/en-us/docs/download/release-0.7.0.json
+++ b/en-us/docs/download/release-0.7.0.json
@@ -1,8 +1,8 @@
{
"filename": "release-0.7.0.md",
- "__html": "<h1>Download the inlong releases</h1>\n<p>Use the links below to download the Apache inlong from one of our mirrors.</p>\n<h2>inlong</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">December. 4th, 2020</td>\n<td style=\"text-align:center\">0.7.0</td>\ [...]
+ "__html": "<h1>Download the TubeMQ releases</h1>\n<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>\n<h2>TubeMQ</h2>\n<table>\n<thead>\n<tr>\n<th style=\"text-align:center\">Date</th>\n<th style=\"text-align:center\">Version</th>\n<th style=\"text-align:center\">Comment</th>\n<th style=\"text-align:center\">Downloads</th>\n</tr>\n</thead>\n<tbody>\n<tr>\n<td style=\"text-align:center\">December. 4th, 2020</td>\n<td style=\"text-align:center\">0.7.0</td>\ [...]
"link": "/en-us/docs/download/release-0.7.0.html",
"meta": {
- "title": "Download - Apache inlong"
+ "title": "Download - Apache TubeMQ"
}
}
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.7.0.md b/en-us/docs/download/release-0.7.0.md
index 84a654d..06d8c66 100644
--- a/en-us/docs/download/release-0.7.0.md
+++ b/en-us/docs/download/release-0.7.0.md
@@ -1,17 +1,17 @@
---
-title: Download - Apache inlong
+title: Download - Apache TubeMQ
---
-# Download the inlong releases
+# Download the TubeMQ releases
-Use the links below to download the Apache inlong from one of our mirrors.
+Use the links below to download the Apache TubeMQ from one of our mirrors.
-## inlong
+## TubeMQ
| Date | Version| Comment | Downloads |
|:---:|:--:|:--:|:--:|
-| December. 4th, 2020 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-0.7.0-incubating-src.tar.gz.sha512)] |
-| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-client-0.7.0-incubating-bin.tar.gz.sha512)] |
-| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/inlong/0.7.0-incubating/apache-inlong-server-0.7.0-incubating-bin.tar.gz.sha512)] |
+| December. 4th, 2020 | 0.7.0 | Source | [[SRC](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-0.7.0-incubating-src.tar.gz.sha512)] |
+| | | Client | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-client-0.7.0-incubating-bin.tar.gz.sha512)] |
+| | | Server | [[TAR](http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz)] [[PGP](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.asc)] [[SHA512](https://downloads.apache.org/incubator/tubemq/0.7.0-incubating/apache-tubemq-server-0.7.0-incubating-bin.tar.gz.sha512)] |
## Release Notes
@@ -20,37 +20,37 @@ Use the links below to download the Apache inlong from one of our mirrors.
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-162](https://issues.apache.org/jira/browse/inlong-162) | Python SDK support in inlong | High |
-| [inlong-336](https://issues.apache.org/jira/browse/inlong-336) | Propose web portal to manage tube cluster Phase-I | Major |
-| [inlong-390](https://issues.apache.org/jira/browse/inlong-390) | support build C++ SDK with docker image | Normal |
+| [TUBEMQ-162](https://issues.apache.org/jira/browse/TUBEMQ-162) | Python SDK support in TubeMQ | High |
+| [TUBEMQ-336](https://issues.apache.org/jira/browse/TUBEMQ-336) | Propose web portal to manage tube cluster Phase-I | Major |
+| [TUBEMQ-390](https://issues.apache.org/jira/browse/TUBEMQ-390) | support build C++ SDK with docker image | Normal |
### IMPROVEMENTS:
| JIRA | Summary | Priority |
| :---- | :------- | :------- |
-| [inlong-369](https://issues.apache.org/jira/browse/inlong-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
-| [inlong-373](https://issues.apache.org/jira/browse/inlong-373) | Reduce the redundant code of Utils::Split functions | Major |
-| [inlong-374](https://issues.apache.org/jira/browse/inlong-374) | Adjust some coding style issues | Major |
-| [inlong-375](https://issues.apache.org/jira/browse/inlong-375) | Add a section to the README file about how to compile the project| Major |
-| [inlong-385](https://issues.apache.org/jira/browse/inlong-385) | update docker images | Major |
-| [inlong-393](https://issues.apache.org/jira/browse/inlong-393) | Optimize the mapping code of WEB API | Major |
-| [inlong-406](https://issues.apache.org/jira/browse/inlong-406) | test_consumer.py works for both Python 2 and 3 | Minor |
-| [inlong-410](https://issues.apache.org/jira/browse/inlong-410) | install python package and simplify test_consumer.py | Major |
-| [inlong-416](https://issues.apache.org/jira/browse/inlong-416) | support consume from specified position | Major |
-| [inlong-417](https://issues.apache.org/jira/browse/inlong-417) | C++ Client support parse message from binary data for Python SDK | Major |
-| [inlong-419](https://issues.apache.org/jira/browse/inlong-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
+| [TUBEMQ-369](https://issues.apache.org/jira/browse/TUBEMQ-369) | hope to add an option in the compilation script (like `make lib` etc...) | Major |
+| [TUBEMQ-373](https://issues.apache.org/jira/browse/TUBEMQ-373) | Reduce the redundant code of Utils::Split functions | Major |
+| [TUBEMQ-374](https://issues.apache.org/jira/browse/TUBEMQ-374) | Adjust some coding style issues | Major |
+| [TUBEMQ-375](https://issues.apache.org/jira/browse/TUBEMQ-375) | Add a section to the README file about how to compile the project| Major |
+| [TUBEMQ-385](https://issues.apache.org/jira/browse/TUBEMQ-385) | update docker images | Major |
+| [TUBEMQ-393](https://issues.apache.org/jira/browse/TUBEMQ-393) | Optimize the mapping code of WEB API | Major |
+| [TUBEMQ-406](https://issues.apache.org/jira/browse/TUBEMQ-406) | test_consumer.py works for both Python 2 and 3 | Minor |
+| [TUBEMQ-410](https://issues.apache.org/jira/browse/TUBEMQ-410) | install python package and simplify test_consumer.py | Major |
+| [TUBEMQ-416](https://issues.apache.org/jira/browse/TUBEMQ-416) | support consume from specified position | Major |
+| [TUBEMQ-417](https://issues.apache.org/jira/browse/TUBEMQ-417) | C++ Client support parse message from binary data for Python SDK | Major |
+| [TUBEMQ-419](https://issues.apache.org/jira/browse/TUBEMQ-419) | SetMaxPartCheckPeriodMs() negative number, getMessage() still | Major |
### BUG FIXES:
| JIRA | Summary | Priority |
| :----------------------------------------------------------- | :----------------------------------------------------------- | :------- |
-| [inlong-365](https://issues.apache.org/jira/browse/inlong-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
-| [inlong-370](https://issues.apache.org/jira/browse/inlong-370) | Calling GetCurConsumedInfo API always returns failure | Major |
-| [inlong-376](https://issues.apache.org/jira/browse/inlong-376) | Move pullrequests_status notifications commits mail list | Major |
-| [inlong-366](https://issues.apache.org/jira/browse/inlong-366) | Found a nullpointerexception bug in broker | Normal |
-| [inlong-379](https://issues.apache.org/jira/browse/inlong-379) | Modify the memory cache size default to 3M | Normal |
-| [inlong-380](https://issues.apache.org/jira/browse/inlong-380) | Cpp client link error when gcc optimization is disabled | Major |
-| [inlong-405](https://issues.apache.org/jira/browse/inlong-405) | python sdk install files lack of the whole cpp configuration | Major |
-| [inlong-401](https://issues.apache.org/jira/browse/inlong-401) | python sdk readme bug | Minor |
-| [inlong-407](https://issues.apache.org/jira/browse/inlong-407) | Fix some content in README.md | Trivial |
-| [inlong-418](https://issues.apache.org/jira/browse/inlong-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
\ No newline at end of file
+| [TUBEMQ-365](https://issues.apache.org/jira/browse/TUBEMQ-365) | Whether the consumption setting is wrong after the processRequest exception | Major |
+| [TUBEMQ-370](https://issues.apache.org/jira/browse/TUBEMQ-370) | Calling GetCurConsumedInfo API always returns failure | Major |
+| [TUBEMQ-376](https://issues.apache.org/jira/browse/TUBEMQ-376) | Move pullrequests_status notifications commits mail list | Major |
+| [TUBEMQ-366](https://issues.apache.org/jira/browse/TUBEMQ-366) | Found a nullpointerexception bug in broker | Normal |
+| [TUBEMQ-379](https://issues.apache.org/jira/browse/TUBEMQ-379) | Modify the memory cache size default to 3M | Normal |
+| [TUBEMQ-380](https://issues.apache.org/jira/browse/TUBEMQ-380) | Cpp client link error when gcc optimization is disabled | Major |
+| [TUBEMQ-405](https://issues.apache.org/jira/browse/TUBEMQ-405) | python sdk install files lack of the whole cpp configuration | Major |
+| [TUBEMQ-401](https://issues.apache.org/jira/browse/TUBEMQ-401) | python sdk readme bug | Minor |
+| [TUBEMQ-407](https://issues.apache.org/jira/browse/TUBEMQ-407) | Fix some content in README.md | Trivial |
+| [TUBEMQ-418](https://issues.apache.org/jira/browse/TUBEMQ-418) | C++ SDK function SetMaxPartCheckPeriodMs() can't work | Major |
\ No newline at end of file
diff --git a/en-us/docs/download/release-0.8.0.html b/en-us/docs/download/release-0.8.0.html
index 150e570..2c8e93e 100644
--- a/en-us/docs/download/release-0.8.0.html
+++ b/en-us/docs/download/release-0.8.0.html
@@ -7,14 +7,14 @@
<meta name="keywords" content="release-0.8.0" />
<meta name="description" content="release-0.8.0" />
<!-- 网页标签标题 -->
- <title>Download - Apache inlong</title>
+ <title>Download - Apache TubeMQ</title>
<link rel="shortcut icon" href="/img/apache.ico"/>
<link rel="stylesheet" href="/build/documentation.css" />
</head>
<body>
- <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
-<p>Use the links below to download the Apache inlong from one of our mirrors.</p>
-<h2>inlong</h2>
+ <div id="root"><div class="documentation-page" data-reactroot=""><header class="header-container header-container-normal"><div class="header-body"><a href="/en-us/index.html"><a href="//www.apache.org"><img class="logo apache" style="width:120px" src="/img/asf_logo.svg"/></a><div class="logo-split"></div><a href=""></a><img class="logo tube" style="width:72px" src="/img/Tube logo.svg"/></a><div class="search search-normal"><span class="icon-search"></span></div><span class="language-swi [...]
+<p>Use the links below to download the Apache TubeMQ from one of our mirrors.</p>
+<h2>TubeMQ</h2>
<table>
<thead>
<tr>
@@ -29,19 +29,19 @@
<td style="text-align:center">March. 4th, 2021</td>
<td style="text-align:center">0.8.0</td>
<td style="text-align:center">Source</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-0.8.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz">SRC</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-0.8.0-incubating-src.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Client</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-client-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-client-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
<tr>
<td style="text-align:center"></td>
<td style="text-align:center"></td>
<td style="text-align:center">Server</td>
-<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/inlong/0.8.0-incubating/apache-inlong-server-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
+<td style="text-align:center">[<a href="http://www.apache.org/dyn/closer.lua/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz">TAR</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.asc">PGP</a>] [<a href="https://downloads.apache.org/incubator/tubemq/0.8.0-incubating/apache-tubemq-server-0.8.0-incubating-bin.tar.gz.sha512">SHA512</a>]</td>
</tr>
</tbody>
</table>
@@ -57,57 +57,57 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-430">inlong-430</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-430">TUBEMQ-430</a></td>
<td style="text-align:left">Optimizing the implementation of HTTP API for broke</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-445">inlong-445</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-445">TUBEMQ-445</a></td>
<td style="text-align:left">Adjust the status check default sleep interval of pullConsumeReadyChkSliceMs</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-448">inlong-448</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-448">TUBEMQ-448</a></td>
<td style="text-align:left">Add Committer and PPMC operation process</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-449">inlong-449</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-449">TUBEMQ-449</a></td>
<td style="text-align:left">Adjust Example implementation</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-452">inlong-452</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-452">TUBEMQ-452</a></td>
<td style="text-align:left">Optimize rebalance performance</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-467">inlong-467</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-467">TUBEMQ-467</a></td>
<td style="text-align:left">Add WEB APIs of Master and Broker</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-489">inlong-489</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-489">TUBEMQ-489</a></td>
<td style="text-align:left">Add the maximum message length parameter setting</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-495">inlong-495</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-495">TUBEMQ-495</a></td>
<td style="text-align:left">Code implementation adjustment based on SpotBugs check</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-511">inlong-511</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-511">TUBEMQ-511</a></td>
<td style="text-align:left">Replace the conditional operator (?:) with mid()</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-512">inlong-512</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-512">TUBEMQ-512</a></td>
<td style="text-align:left">Add package length control based on Topic</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-515">inlong-515</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-515">TUBEMQ-515</a></td>
<td style="text-align:left">Add cluster Topic view web api</td>
<td style="text-align:left">Major</td>
</tr>
@@ -124,67 +124,67 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-437">inlong-437</a></td>
-<td style="text-align:left">Fix inlong table source sink factory instance creating problem</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-437">TUBEMQ-437</a></td>
+<td style="text-align:left">Fix tubemq table source sink factory instance creating problem</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-441">inlong-441</a></td>
-<td style="text-align:left">An error occurred when using the inlong class to create a sink table</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-441">TUBEMQ-441</a></td>
+<td style="text-align:left">An error occurred when using the Tubemq class to create a sink table</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-442">inlong-442</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-442">TUBEMQ-442</a></td>
<td style="text-align:left">Modifying the jvm parameters when the broker starts does not take effect</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-443">inlong-443</a></td>
-<td style="text-align:left">inlongSourceFunction class prints too many logs problem</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-443">TUBEMQ-443</a></td>
+<td style="text-align:left">TubemqSourceFunction class prints too many logs problem</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-446">inlong-446</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-446">TUBEMQ-446</a></td>
<td style="text-align:left">Small bugs fix that do not affect the main logics</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-450">inlong-450</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-450">TUBEMQ-450</a></td>
<td style="text-align:left">TubeClientException: Generate producer id failed</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-453">inlong-453</a></td>
-<td style="text-align:left">inlongSourceFunction class prints too many logs problem</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-453">TUBEMQ-453</a></td>
+<td style="text-align:left">TubemqSourceFunction class prints too many logs problem</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-506">inlong-506</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-506">TUBEMQ-506</a></td>
<td style="text-align:left">cmakelist error</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-510">inlong-510</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-510">TUBEMQ-510</a></td>
<td style="text-align:left">Found a bug in MessageProducerExample class</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-518">inlong-518</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-518">TUBEMQ-518</a></td>
<td style="text-align:left">fix parameter pass error</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-526">inlong-526</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-526">TUBEMQ-526</a></td>
<td style="text-align:left">Adjust the packaging script and version check list, remove the "-WIP" tag</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-555">inlong-555</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-555">TUBEMQ-555</a></td>
<td style="text-align:left">short session data can only be written to a specific partition</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-556">inlong-556</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-556">TUBEMQ-556</a></td>
<td style="text-align:left">Index value is bigger than the actual number of records</td>
<td style="text-align:left">Low</td>
</tr>
@@ -201,22 +201,22 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-505">inlong-505</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-505">TUBEMQ-505</a></td>
<td style="text-align:left">Remove the "WIP" label of the DISCLAIMER file</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-543">inlong-543</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-543">TUBEMQ-543</a></td>
<td style="text-align:left">Modify the LICENSE statement of multiple files and others</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-557">inlong-557</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-557">TUBEMQ-557</a></td>
<td style="text-align:left">Handle the issues mentioned in the 0.8.0-RC2 review</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-562">inlong-562</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-562">TUBEMQ-562</a></td>
<td style="text-align:left">Update project contents according to the 0.8.0-RC3 review</td>
<td style="text-align:left">Major</td>
</tr>
@@ -233,202 +233,202 @@
</thead>
<tbody>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-433">inlong-428</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-433">TUBEMQ-428</a></td>
<td style="text-align:left">Bumped version to 0.8.0-SNAPSHOT</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-433">inlong-433</a></td>
-<td style="text-align:left">add inlong perf-consumer/producer scripts</td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-433">TUBEMQ-433</a></td>
+<td style="text-align:left">add tubemq perf-consumer/producer scripts</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-434">inlong-434</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-434">TUBEMQ-434</a></td>
<td style="text-align:left">Adjust Broker API mapping</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-435">inlong-435</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-435">TUBEMQ-435</a></td>
<td style="text-align:left">Create Web field Mapping</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-436">inlong-436</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-436">TUBEMQ-436</a></td>
<td style="text-align:left">Adjust Broker's HTTP API implementation</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-439">inlong-439</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-439">TUBEMQ-439</a></td>
<td style="text-align:left">Add Cli field Scheme definition</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-440">inlong-440</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-440">TUBEMQ-440</a></td>
<td style="text-align:left">Add feature package tube-manager to zip</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-444">inlong-444</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-444">TUBEMQ-444</a></td>
<td style="text-align:left">Add consume and produce Cli commands</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-447">inlong-447</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-447">TUBEMQ-447</a></td>
<td style="text-align:left">Add Broker-Admin Cli</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-451">inlong-451</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-451">TUBEMQ-451</a></td>
<td style="text-align:left">Replace ConsumeTupleInfo with Tuple2</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-457">inlong-457</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-457">TUBEMQ-457</a></td>
<td style="text-align:left">There is no need to return StringBuilder in Master.java</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-463">inlong-463</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-463">TUBEMQ-463</a></td>
<td style="text-align:left">Adjust Master rebalance process implementation</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-464">inlong-464</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-464">TUBEMQ-464</a></td>
<td style="text-align:left">Add parameter rebalanceParallel in master.ini</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-470">inlong-470</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-470">TUBEMQ-470</a></td>
<td style="text-align:left">Add query API of TopicName and BrokerId collection</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-471">inlong-471</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-471">TUBEMQ-471</a></td>
<td style="text-align:left">Add query API Introduction of TopicName and BrokerId collection</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-472">inlong-472</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-472">TUBEMQ-472</a></td>
<td style="text-align:left">Adjust Broker's AbstractWebHandler class implementation</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-475">inlong-475</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-475">TUBEMQ-475</a></td>
<td style="text-align:left">add the offset clone api of the consume group</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-482">inlong-482</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-482">TUBEMQ-482</a></td>
<td style="text-align:left">Add offset query api</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-484">inlong-484</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-484">TUBEMQ-484</a></td>
<td style="text-align:left">Add query API for topic publication information</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-485">inlong-485</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-485">TUBEMQ-485</a></td>
<td style="text-align:left">Add the batch setting API of consume group offset</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-486">inlong-486</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-486">TUBEMQ-486</a></td>
<td style="text-align:left">Add the delete API of consumer group offset</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-494">inlong-494</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-494">TUBEMQ-494</a></td>
<td style="text-align:left">Update API interface instruction document</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-499">inlong-499</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-499">TUBEMQ-499</a></td>
<td style="text-align:left">Add configure store</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-500">inlong-500</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-500">TUBEMQ-500</a></td>
<td style="text-align:left">Add setting operate API</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-501">inlong-501</a></td>
+<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/TUBEMQ-501">TUBEMQ-501</a></td>
<td style="text-align:left">Adjust max message size check logic</td>
<td style="text-align:left">Major</td>
</tr>
<tr>
-<td style="text-align:left"><a href="https://issues.apache.org/jira/browse/inlong-502">inlong-502</a></td>
... 7096 lines suppressed ...