[
https://issues.apache.org/jira/browse/NIFI-11995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Handermann resolved NIFI-11995.
-------------------------------------
Fix Version/s: 2.0.0
1.24.0
(was: 1.latest)
(was: 2.latest)
Assignee: Umar Hussain
Resolution: Fixed
> ComsumeAMQP: Support multiple header output formats
> ---------------------------------------------------
>
> Key: NIFI-11995
> URL: https://issues.apache.org/jira/browse/NIFI-11995
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.23.2
> Reporter: Umar Hussain
> Assignee: Umar Hussain
> Priority: Minor
> Fix For: 2.0.0, 1.24.0
>
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Currently, the ConsumeAMQP outputs headers as string with comma separated
> items and {{=}} between key and value for each header. There is also an
> option to enable/disable curly braces. I find it difficult to parse this
> string and get values from it. Examples are:
> {code:java}
> {result=success,customerId=customer1,outputType=application/pdf,correlationId=82f1b849-6745-49b4-941b-e86e5c5a71a6,applicationId=nifi,contentType=application/pdf,responseId=3241343a}
> {code}
> The idea is to extend the processor to output the value as a valid JSON
> string as well so that we can later parse it with jsonpath for example.
> Another option is to add the ability to put each rabbitmq header key as
> flowfile attribute with some prefix like {{consume.amqp.}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
