This is an automated email from the ASF dual-hosted git repository.
wlliqipeng pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git
The following commit(s) were added to refs/heads/develop by this push:
new 161a457 Update Design_Filter.md
new de34ce7 Merge pull request #985 from SessionBest/develop
161a457 is described below
commit 161a4572b68c5b2fcea258a1ecbbf37053c4df99
Author: Brain <[email protected]>
AuthorDate: Sun Mar 3 12:20:25 2019 +0800
Update Design_Filter.md
---
docs/en/Design_Filter.md | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/en/Design_Filter.md b/docs/en/Design_Filter.md
index 246e162..28eb599 100644
--- a/docs/en/Design_Filter.md
+++ b/docs/en/Design_Filter.md
@@ -5,6 +5,6 @@ RocketMQ - a distributed message queue, is different with all
other MQ middlewar
The RocketMQ has two mainly filter types:
-* Tag filtering: Consumer can specify not only the message topic but also the
message tag values, when subscribing. Multiple tag values need to be separated
by '||'. When consumer subscribing a message, it builds the subscription
request into a `SubscriptionData` object and sends a Pull message request to
the Broker side. Before the Broker side reads data from the RocketMQ file
storage layer - Store, it will construct a `MessageFilter` using the
`SubscriptionData` object and then pass it [...]
+* Tag filtering: Consumer can specify not only the message topic but also the
message tag values, when subscribing. Multiple tag values need to be separated
by '||'. When consumer subscribing a message, it builds the subscription
request into a `SubscriptionData` object and sends a pull message request to
the Broker side. Before the Broker side reads data from the RocketMQ file
storage layer - Store, it will construct a `MessageFilter` using the
`SubscriptionData` object and then pass it [...]
-* SQL92 filtering: This filter behavior is almost same with the above Tag
filtering method. The only difference is on the way how Store works. The
rocketmq-filter module is responsible for the construction and execution of the
real SQL expression. Executing an SQL expression every time a filter is
executed affects efficiency, so RocketMQ uses BloomFilter to avoid doing it
every time. The expression context of SQL92 is a property of the message.
+* SQL92 filtering: This filter behavior is almost same with the above `Tag
filtering` method. The only difference is on the way how Store works. The
rocketmq-filter module is responsible for the construction and execution of the
real SQL expression. Executing an SQL expression every time a filter is
executed affects efficiency, so RocketMQ uses BloomFilter to avoid doing it
every time. The expression context of SQL92 is a property of the message.
