315157973 commented on issue #12269: URL: https://github.com/apache/pulsar/issues/12269#issuecomment-951756445
> > 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 > > I aggreed. If we want to modify the data of a specific Entry, currently we could only use funtions. If we could modify Entry data in broker side directly, we could save much network workload. But it's not a good way to let user deserialize Entry data to heap, we could try to consider how to modify Entry data in broker side with a efficiency way and reduce the GC workload on the broker. Maybe we could create another PIP for how to modify the data of entry, since this PIP is for entry filter. If I just need to filter based on the content of the message, and the developer can tolerate the CPU and memory usage, why not? -- 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]
