houxiaoyu

> 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...

Hi Asaf @asafm > Is this true now or do you plan to enforce it? This is what I plan to enforce it. The batch entry metadata properties is empty...

> Might generate smaller batches or increase latency? Yes. This will generate smaller batches if `batchedFilterProperties ` is not empty. But the advantage is that there is no need to...

> What I am suggesting is to turn this idea a bit: Instead of batching per the same values of keys, batch all messages, and for each property save a...

Thank you for your patience @asafm . Yes, what you described above is correctly. > All I wrote above is not clearly stated in the PIP. IMO the PIP needs...

> Why not do like the BatchMessageKeyBasedContainer and create your own - I have considered this solution before. `BatchMessageKeyBasedContainer` doesn't keep message's order because it is just used for key_shared...

> Can you explain how in your proposal, you keep the exact ordering of the messages as they were sent to the producer while separating them into different batches based...

> I expected it at this stage to create a batch for region=us and add M2 to it. But I see written in your diagram that you "batched msgs in...

> I would for sure document that trade-off very clearly in the PIP and in the configuration page of the producer. OK. Thanks for your suggestions @asafm . I have...

> What ended up with this feature? There was a VOTE[1] about this PIP and end up with 1 bingding -1 and 1 non-bing +1. So maybe this feature need...