315157973 commented on issue #12269: URL: https://github.com/apache/pulsar/issues/12269#issuecomment-951729337
> > 1. The parsed header information is already in the `FilterContext`, and you don't even need to re-parse the metadata. The incoming parameter is an Entry, you can play freely. You can even modify the data in Entry. > > If user want to play anything with `Entry` parameter, user need to deserialize entire Entry to heap in their implement, then user could modify the data in Entry. As @codelipenghui suggested in [#11962 (comment)](https://github.com/apache/pulsar/issues/11962#issuecomment-915716242), we should avoid to deserialize Entry to heap which will bring more GC workload on the broker. If we do not want user to do this, we could remove the Entry parameter. The framework will not deserialize the entry. Whether it will deserialize it depends on the developer. Entry as a parameter is necessary, we can also be used in many other scenarios , for example: modify the data of a specific Entry -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
