You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Aljoscha Krettek (Jira)" <ji...@apache.org> on 2020/05/05 07:59:00 UTC
[jira] [Commented] (FLINK-17502) Give RMQ deserialization schema
access to more RMQ information
[ https://issues.apache.org/jira/browse/FLINK-17502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17099624#comment-17099624 ]
Aljoscha Krettek commented on FLINK-17502:
------------------------------------------
We should also close FLINK-8510 when we close this.
> Give RMQ deserialization schema access to more RMQ information
> --------------------------------------------------------------
>
> Key: FLINK-17502
> URL: https://issues.apache.org/jira/browse/FLINK-17502
> Project: Flink
> Issue Type: Improvement
> Components: Connectors/ RabbitMQ
> Reporter: Karim Mansour
> Assignee: Karim Mansour
> Priority: Major
>
> Currently the {{RMQSource}} is extracting the body of the message which is a byte array and pass it to a an instance of a user implementation of the {{DeserializationSchema}} class to deserialize the body of the message. It also uses the correlation id from the message properties to deduplicate the message.
> What will be done is creating a new {{RMQSource}} constructor that is instead of taking a implementation of a {{DeserializationSchema}} in the {{RMQSource}} constructor, actually have the user implement an interface that would have methods to extract both the correlation id and message not only from the body of the message but also from it's metadata and properties thus giving the connector much more power and flexibility.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)