This is an automated email from the ASF dual-hosted git repository. duhengforever pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/rocketmq-site.git
commit 804fae56d936639eebf7a4d5eeba6d0a234d4950 Author: duhengforever <[email protected]> AuthorDate: Fri Nov 2 22:14:31 2018 +0800 Add 4.3.2 release note --- _docs/25-rmq-transaction-example.md | 2 +- _posts/2018-11-03-release-notes-4.3.2.md | 56 ++++++++++++++++++++++++++++++++ 2 files changed, 57 insertions(+), 1 deletion(-) diff --git a/_docs/25-rmq-transaction-example.md b/_docs/25-rmq-transaction-example.md index abdb99f..1d8592a 100644 --- a/_docs/25-rmq-transaction-example.md +++ b/_docs/25-rmq-transaction-example.md @@ -19,7 +19,7 @@ Transactional message ensures that the execution of local transaction and the se (1) Messages of the transactional have no schedule and batch support. (2) In order to avoid a single message being checked too many times and lead to half queue message accumulation， we limited the number of checks for a single message to 15 times by default, but users can change this limit by change the "transactionCheckMax" parameter in the configuration of the broker， if one message has been checked over "transactionCheckMax" times， broker will discard this message and print an error log at the same time by default. Users can change this behavior by ove [...] -(3) A transactional message will be checked after a certain period of time that determined by parameter "transactionMsgTimeout" in the configuration of the broker. And users also can change this limit by set user property "CHECK_IMMUNITY_TIME_IN_SECONDS" when sending transactional message, this parameter takes precedence over the "transactionMsgTimeout" parameter. +(3) A transactional message will be checked after a certain period of time that determined by parameter "transactionTimeout" in the configuration of the broker. And users also can change this limit by set user property "CHECK_IMMUNITY_TIME_IN_SECONDS" when sending transactional message, this parameter takes precedence over the "transactionMsgTimeout" parameter. (4) A transactional message maybe checked or consumed more than once. (5) Committed message reput to the user's target topic may fail. Currently, it depends on the log record. High availability is ensured by the high availability mechanism of RocketMQ itself. If you want to ensure that the transactional message isn't lost and the transaction integrity is guaranteed, it is recommended to use synchronous double write. mechanism. (6) Producer IDs of transactional messages cannot be shared with producer IDs of other types of messages. Unlike other types of message, transactional messages allow backward queries. MQ Server query clients by their Producer IDs. diff --git a/_posts/2018-11-03-release-notes-4.3.2.md b/_posts/2018-11-03-release-notes-4.3.2.md new file mode 100644 index 0000000..7a115ad --- /dev/null +++ b/_posts/2018-11-03-release-notes-4.3.2.md @@ -0,0 +1,56 @@ +--- +title: "Release Notes - Apache RocketMQ - Version 4.3.2" +categories: + - Release_Notes +tags: + - Release_Notes + - RocketMQ + - Version +--- + +Below is a summary of the issues addressed in the 4.3.2 release of RocketMQ. For full documentation of the release, a guide to get started, please refer to <a href='/docs/quick-start/'>Quick Start</a>. + + +<h2> Download the 4.3.2 release</h2> + +* Source: [rocketmq-all-4.3.2-source-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.3.2/rocketmq-all-4.3.2-source-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-source-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-source-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-source-release.zip.sha1)] +* Binary: [rocketmq-all-4.3.2-bin-release.zip](https://www.apache.org/dyn/closer.cgi?path=rocketmq/4.3.2/rocketmq-all-4.3.2-bin-release.zip) [[PGP](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-bin-release.zip.asc)] [[MD5](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-bin-release.zip.md5)] [[SHA1](https://www.apache.org/dist/rocketmq/4.3.2/rocketmq-all-4.3.2-bin-release.zip.sha1)] + +## New Feature +<ul> +<li>[<a href='https://github.com/apache/rocketmq/issues/462'>ISSUE-462</a>] - Add the python [client](https://github.com/apache/rocketmq-client-python), which is based on the encapsulation of the C interface. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/488'>ISSUE-488</a>] - Add the C/C++ [client](https://github.com/apache/rocketmq-client-cpp). A bunch of other client will be built on top of it, including Python, node.js, go .The C/C++ Client with robust high performance support for produce, pull/push consumer, etc. +</li> +</ul> + + + +## Improvement +<ul> +<li>[<a href='https://github.com/apache/rocketmq/issues/411'>ISSUE-411</a>] - Fixed ClassCastException when get the instance of the store. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/461'>ISSUE-461</a>] - Purge filterserv related code in client. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/478'>ISSUE-478</a>] - Polish async send message sample. +</li> +</ul> + +## Bug + +<ul> +<li>[<a href='https://github.com/apache/rocketmq/issues/406'>ISSUE-406</a>] - Fixed the NPE issue occurred when getting the storehost using admin tool. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/433'>ISSUE-433</a>] - Fixed the issue that Integration-test can not be executed when run "mvn clean install". +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/439'>ISSUE-439</a>] - Fixed the issue that ConsumeMessageCommand -g setting. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/447'>ISSUE-447</a>] - Fix the issue that checkLocalTransaction method does not take effect. +</li> +<li>[<a href='https://github.com/apache/rocketmq/issues/490'>ISSUE-490</a>] - Fix the issue that testGetLocalInetAddress failure on some versions of the server. +</li> +</ul> + + + +
