You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Fil Karnicki (Jira)" <ji...@apache.org> on 2022/04/08 14:07:00 UTC

[jira] [Commented] (FLINK-26617) Pass Kafka headers to remote functions and egresses

    [ https://issues.apache.org/jira/browse/FLINK-26617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17519583#comment-17519583 ] 

Fil Karnicki commented on FLINK-26617:
--------------------------------------

Hi [~trohrmann], I think that my requirements can be serviced by using the datastream api, which can merge kafka headers into the business object, making them available inside the remote function. Therefore, this ticket can probably be closed, as another one around OpenTracing (these days OpenTelemetry) exists - [FLINK-22390|https://issues.apache.org/jira/browse/FLINK-22390]. What do you think?

> Pass Kafka headers to remote functions and egresses
> ---------------------------------------------------
>
>                 Key: FLINK-26617
>                 URL: https://issues.apache.org/jira/browse/FLINK-26617
>             Project: Flink
>          Issue Type: Improvement
>          Components: Stateful Functions
>            Reporter: Fil Karnicki
>            Priority: Minor
>
> Typically OpenTelemetry (FLINK-22390) tracing spans get passed in kafka headers. We could be passing not only the Kafka ConsumerRecord value, but also the headers to remote functions, if the user configures their kafka ingress to do so
> Similarly, kafka egresses could be configurable so that headers get passed on via the KafkaProducerRecord proto to kafka



--
This message was sent by Atlassian Jira
(v8.20.1#820001)