You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by Maxim Fortun <ma...@maxf.net> on 2024/08/06 13:21:10 UTC

Kafka PR16802: Custom produce request parsers

CONTRIBUTING doc says to nag :)
Please check out my PR that adds server side ability to intercept incoming messages. My org needs to be able to apply lineage and certain other tiny transforms to all the messages on the server side, and this feature would allow us to adopt Kafka. 
The alternatives of using a client side solution(like streams) or creating a proxy in front of Kafka is a very heavy lift and we would prefer to avoid it. 
If there are other ways to intercept an incoming message and manipulate it, please point me in the right direction. 
Thanks!
Max


https://github.com/apache/kafka/pull/16802
add custom produce request parsers by maxfortun · Pull Request #16802 · apache/kafka
github.com


Re: Kafka PR16802: Custom produce request parsers

Posted by Chia-Ping Tsai <ch...@gmail.com>.
hi Maxim

I don't have all contexts about PR#16802 , but I hope following suggestions
is useful to you.

1. please file jira first as the changes you proposed are not small

2. please write KIP if the changes are related to public stuff

3. please have patience as there are too many PRs in this huge project

Best,
Chia-Ping

Maxim Fortun <ma...@maxf.net> 於 2024年8月7日 週三 下午6:18寫道:

> My Apologies, the branch was misnamed. The new PR is 16812.
>
> [image: 16812.png]
>
> Feature/add custom produce request parsers by maxfortun · Pull Request
> #16812 · apache/kafka <https://github.com/apache/kafka/pull/16812>
> github.com <https://github.com/apache/kafka/pull/16812>
> <https://github.com/apache/kafka/pull/16812>
>
>
> On Aug 6, 2024, at 9:21 AM, Maxim Fortun <ma...@maxf.net> wrote:
>
> CONTRIBUTING doc says to nag :)
> Please check out my PR that adds server side ability to intercept incoming
> messages. My org needs to be able to apply lineage and certain other tiny
> transforms to all the messages on the server side, and this feature would
> allow us to adopt Kafka.
> The alternatives of using a client side solution(like streams) or creating
> a proxy in front of Kafka is a very heavy lift and we would prefer to avoid
> it.
> If there are other ways to intercept an incoming message and manipulate
> it, please point me in the right direction.
> Thanks!
> Max
>
>
> <16802.png>
>
> add custom produce request parsers by maxfortun · Pull Request #16802 ·
> apache/kafka <https://github.com/apache/kafka/pull/16802>
> github.com <https://github.com/apache/kafka/pull/16802>
> <https://github.com/apache/kafka/pull/16802>
>
>
>

Re: Kafka PR16802: Custom produce request parsers

Posted by Maxim Fortun <ma...@maxf.net>.
My Apologies, the branch was misnamed. The new PR is 16812.

https://github.com/apache/kafka/pull/16812
Feature/add custom produce request parsers by maxfortun · Pull Request #16812 · apache/kafka
github.com


> On Aug 6, 2024, at 9:21 AM, Maxim Fortun <ma...@maxf.net> wrote:
> 
> CONTRIBUTING doc says to nag :)
> Please check out my PR that adds server side ability to intercept incoming messages. My org needs to be able to apply lineage and certain other tiny transforms to all the messages on the server side, and this feature would allow us to adopt Kafka. 
> The alternatives of using a client side solution(like streams) or creating a proxy in front of Kafka is a very heavy lift and we would prefer to avoid it. 
> If there are other ways to intercept an incoming message and manipulate it, please point me in the right direction. 
> Thanks!
> Max
> 
> 
> https://github.com/apache/kafka/pull/16802
>