[
https://issues.apache.org/jira/browse/ROCKETMQ-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16046300#comment-16046300
]
ASF GitHub Bot commented on ROCKETMQ-121:
-----------------------------------------
Github user vsair commented on the issue:
https://github.com/apache/incubator-rocketmq/pull/82
Hi, Jaskey;
Thanks for your question.
1. It will decode the properties to do calculation at that case.
2. When they are changed, the consumer's subscription will be ignored when
starting, so the results int bloom filter also will be ignored. That is
mean server will do calculation again and not update the results already
existed in Store.
Thanks,
Vsair
On Mon, Jun 12, 2017 at 2:47 PM, Jaskey <[email protected]> wrote:
> @vsair <https://github.com/vsair>
>
> I have two things to confirms,
>
> 1.
>
> if the old messages which exists before consumer subscribe with the
> filter expression must be filtered by decodng properties to do
calculation ?
> 2.
>
> `expectConsumerNumUseFilter = 32` and `maxErrorRateOfBloomFilter =
20` can be configured and changed, what if I change this value and restart,
does the calculated results in the ConsumeQueueExt updated accordingly?
>
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
>
<https://github.com/apache/incubator-rocketmq/pull/82#issuecomment-307704104>,
> or mute the thread
>
<https://github.com/notifications/unsubscribe-auth/ACeujdZf1ZNbu-MycGfHW_kbIuCCvUE3ks5sDN8ZgaJpZM4Mk0bH>
> .
>
> Support message filtering based on SQL92
> ----------------------------------------
>
> Key: ROCKETMQ-121
> URL: https://issues.apache.org/jira/browse/ROCKETMQ-121
> Project: Apache RocketMQ
> Issue Type: New Feature
> Components: rocketmq-client, rocketmq-store
> Reporter: yukon
> Assignee: Eric Liu
> Priority: Minor
> Fix For: 4.1.0-incubating
>
>
> So far, RocketMQ only support message filtering feature by `TAG`, but one
> message only can own one tag, this is too limited to meet complex business
> requirements.
> So, we want to define and implement a reasonable filter language based on a
> subset of the SQL 92 expression syntax to support customized message
> filtering.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
