Here we have the scenario where the message properties are named with /, e.g. a/b/c. To filter those attributes, we're eager on the enhancement of SQL filterting that is able to handle special characters such as /.
We've tried defining / in the ID of org.apache.rocketmq.filter.parser.SelectorParser but it didn't worked as expected, the error message is like
Caused by: com.alipay.sofa.sofamq.org.shade.apache.rocketmq.client.exception.MQClientException: CODE: 23 DESC: org.apache.rocketmq.filter.parser.TokenMgrError: Lexical error at line 1, column 3. Encountered: "b" (98), after : "/"
Here we have the scenario where the message properties are named with
/
, e.g.a/b/c
. To filter those attributes, we're eager on the enhancement of SQL filterting that is able to handle special characters such as/
.We've tried defining
/
in theID
oforg.apache.rocketmq.filter.parser.SelectorParser
but it didn't worked as expected, the error message is like Caused by: com.alipay.sofa.sofamq.org.shade.apache.rocketmq.client.exception.MQClientException: CODE: 23 DESC: org.apache.rocketmq.filter.parser.TokenMgrError: Lexical error at line 1, column 3. Encountered: "b" (98), after : "/"