You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Alpha Diallo (Jira)" <ji...@apache.org> on 2023/03/13 21:17:00 UTC
[jira] [Updated] (FLINK-31428) Add user callbacks to PulsarSource and PulsarSink
[ https://issues.apache.org/jira/browse/FLINK-31428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alpha Diallo updated FLINK-31428:
---------------------------------
Description:
We'd like to add support for user callbacks in {{PulsarSource}} and {{{}PulsarSink{}}}. This enables specific use cases such as event tracing which requires access to low level message properties such as message IDs after an event is produced, topic partitions, etc...
The functionality required is similar to {{ConsumerInterceptor}} and {{ProducerInterceptor}} in the Pulsar Client. However, there is a case to be made for adding new APIs that would help avoid the extra cost of ser/deser when getting the message body through the {{Message}} interface in the interceptors.
was:
We'd like to add support for user callbacks in {{{{PulsarSource}}}} and {{{}{{PulsarSink}}{}}}. This enables specific use cases such as event tracing which requires access to low level message properties such as message IDs after an event is produced, topic partitions, etc...
The functionality required is similar to {{ConsumerInterceptor}} and {{ProducerInterceptor}} in the Pulsar Client. However, there is a case to be made for adding new APIs that would help avoid the extra cost of ser/deser when getting the message body through the {{Message}} interface in the interceptors.
> Add user callbacks to PulsarSource and PulsarSink
> --------------------------------------------------
>
> Key: FLINK-31428
> URL: https://issues.apache.org/jira/browse/FLINK-31428
> Project: Flink
> Issue Type: New Feature
> Components: Connectors / Pulsar
> Reporter: Alpha Diallo
> Priority: Major
>
> We'd like to add support for user callbacks in {{PulsarSource}} and {{{}PulsarSink{}}}. This enables specific use cases such as event tracing which requires access to low level message properties such as message IDs after an event is produced, topic partitions, etc...
> The functionality required is similar to {{ConsumerInterceptor}} and {{ProducerInterceptor}} in the Pulsar Client. However, there is a case to be made for adding new APIs that would help avoid the extra cost of ser/deser when getting the message body through the {{Message}} interface in the interceptors.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)