[
https://issues.apache.org/jira/browse/KAFKA-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17783143#comment-17783143
]
Vincent Bernardi edited comment on KAFKA-6020 at 11/6/23 9:01 AM:
------------------------------------------------------------------
[~murari.it] note that this could be restricted to deserialization of headers
and not of the payload, and maybe also to standard deserializers (Byte [],
String, JSON), if it helps lighten the load on the broker. Basically _any_
compromise would be acceptable to us to spare the bandwidth.
was (Author: JIRAUSER289746):
[~murari.it] note that this could be restricted to deserialization of headers
and not of the payload, and maybe also to standard deserializers (Byte [],
String, JSON), if it helps lighten the load on the broker. Basically _any_
compromise would be acceptable tu us to spare the bandwidth.
> Broker side filtering
> ---------------------
>
> Key: KAFKA-6020
> URL: https://issues.apache.org/jira/browse/KAFKA-6020
> Project: Kafka
> Issue Type: New Feature
> Components: consumer
> Reporter: Pavel Micka
> Priority: Major
> Labels: needs-kip
>
> Currently, it is not possible to filter messages on broker side. Filtering
> messages on broker side is convenient for filter with very low selectivity
> (one message in few thousands). In my case it means to transfer several GB of
> data to consumer, throw it away, take one message and do it again...
> While I understand that filtering by message body is not feasible (for
> performance reasons), I propose to filter just by message key prefix. This
> can be achieved even without any deserialization, as the prefix to be matched
> can be passed as an array (hence the broker would do just array prefix
> compare).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
