[
https://issues.apache.org/jira/browse/FLINK-8510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8510:
----------------------------------
Labels: stale-major (was: )
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Major but is unassigned and neither itself nor its Sub-Tasks have been updated
for 30 days. I have gone ahead and added a "stale-major" to the issue". If this
ticket is a Major, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Provide access to Delivery envelope in RabbitMQ Source
> ------------------------------------------------------
>
> Key: FLINK-8510
> URL: https://issues.apache.org/jira/browse/FLINK-8510
> Project: Flink
> Issue Type: Improvement
> Components: Connectors/ RabbitMQ
> Reporter: Wojciech Luczkow
> Priority: Major
> Labels: stale-major
>
> Currently RMQSource is limited to get AMQP message body in resulting Stream,
> sometimes it would be good to get access to Envelope
>
> For example
> if subscribing to Topic using Routing Key amq.topic.#
> it is impossible to distinguish whether message came from amq.topic.1 or
> amq.topic.2
>
> Studying current implementation I think the easiest option from consumer
> point of view would be to change RMQSource<OUT> to provide
> Stream<RMQMessage<OUT>> which will break Flink API...
> Another would be to create something like detailedsource with different API -
> provide generic Wrapper with message content <OUT> and Map with message
> properties (and protected method to override and fill that map).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
