[
https://issues.apache.org/jira/browse/FLINK-8510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-8510:
----------------------------------
Labels: auto-deprioritized-major auto-deprioritized-minor (was:
auto-deprioritized-major stale-minor)
Priority: Not a Priority (was: Minor)
This issue was labeled "stale-minor" 7 days ago and has not received any
updates so it is being deprioritized. If this ticket is actually Minor, please
raise the priority and ask a committer to assign you the issue or revive the
public discussion.
> 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: Not a Priority
> Labels: auto-deprioritized-major, auto-deprioritized-minor
>
> 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.20.1#820001)
