Re: [DISCUSS] PIP-191: Support batched message using entry filter

2022-07-24 Thread Anon Hxy
There is an example maybe helpful to understand the properties extraction: - Let's set `batchedFilterProperties`=`` This means only key named `region` and `version`will be extracted to the batch meta properties - Then we have a producer that sends the messges below in order: - `msg1` with pr

Re: [DISCUSS] PIP-191: Support batched message using entry filter

2022-07-21 Thread Anon Hxy
Hi Enrico Thanks for your replying. > 1) It is not clear to me if you want to push all the messages metadata in the main header of the entry or only the metatadata of the first entry, or only the KEY. I just want to copy the partial message properties(we call it batch properties here) to the mai

Re: [DISCUSS] PIP-191: Support batched message using entry filter

2022-07-21 Thread Enrico Olivelli
Thank you for this proposal ! I understand the problem, and I have already thought about it, because I am the author of some filters (especially the JMS Selectors Filter) but we have to clarify more about this PIP. 1) It is not clear to me if you want to push all the messages metadata in the main

Re: [DISCUSS] PIP-191: Support batched message using entry filter

2022-07-21 Thread Qiang Huang
Good. +1 Anon Hxy 于2022年7月19日周二 18:00写道: > Hi Pulsar community: > > I open a pip to discuss "Support batched message using entry filter" > > Proposal Link: https://github.com/apache/pulsar/issues/16680 > --- > > ## Motivation > > We already have a plug-in way to filter entries in broker, aka PI

[DISCUSS] PIP-191: Support batched message using entry filter

2022-07-19 Thread Anon Hxy
Hi Pulsar community: I open a pip to discuss "Support batched message using entry filter" Proposal Link: https://github.com/apache/pulsar/issues/16680 --- ## Motivation We already have a plug-in way to filter entries in broker, aka PIP-105 https://github.com/apache/pulsar/issues/12269. But th