[ https://issues.apache.org/jira/browse/NIFI-4303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16797434#comment-16797434 ]
Mathieu Fortin commented on NIFI-4303: -------------------------------------- It seems nothing has been done on this, which I find surprising since having access to the message provenance looks like a required item for any topic-based amqp consumer. Any pointers on how this should be implemented ? Maybe im wrong but I think the refered code misses the underlying envelope reference, which would be required to have the routing key. I could put some time to produce a PR. > RabbitMQConsumer: Publish the message routing key as an attribute to flowfile > ----------------------------------------------------------------------------- > > Key: NIFI-4303 > URL: https://issues.apache.org/jira/browse/NIFI-4303 > Project: Apache NiFi > Issue Type: Improvement > Reporter: Mehdi Avdi > Priority: Major > Attachments: Screen Shot 2017-08-17 at 15.35.57.png > > > When retrieving messages from a queue that is bound to a topic exchange, > message come with a routing key which might contain crucial identifying > information about where the message came from. > Current implementation of the RabbitMQConsumer processor doesn't publish this > property of the message to the attributes of the flowfile it creates. Can > this be added? > I found the relevant code here: > https://github.com/apache/nifi/blob/d838f61291d2582592754a37314911b701c6891b/nifi-nar-bundles/nifi-amqp-bundle/nifi-amqp-processors/src/main/java/org/apache/nifi/amqp/processors/AMQPUtils.java#L95 > I have very sketchy Java skills, otherwise would submit a PR. -- This message was sent by Atlassian JIRA (v7.6.3#76005)