[jira] [Commented] (NIFI-1686) NiFi is unable to populate over 1/4 of AMQP properties from flow properties

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NIFI-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15224186#comment-15224186 ] 

ASF subversion and git services commented on NIFI-1686:
-------------------------------------------------------

Commit b531b97a4da2fc35b16e5bed0d24028865383ee4 in nifi's branch refs/heads/master from [~steveyh25]
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=b531b97 ]

NIFI-1686 - NiFi is unable to populate over 1/4 of AMQP properties from flow properties


> NiFi is unable to populate over 1/4 of AMQP properties from flow properties
> ---------------------------------------------------------------------------
>
>                 Key: NIFI-1686
>                 URL: https://issues.apache.org/jira/browse/NIFI-1686
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework
>    Affects Versions: 0.5.1
>            Reporter: Stephen Harper
>
> When creating a flow (we used ListenHTTP, but this bug will affect all) that forwards on to a rabbit queue, org.apache.nifi.amqp.processors.PublishAMQP uses the method extractAmqpPropertiesFromFlowFile to populate the AMQP BasicProperties if the flow attributes match a certain format (i.e amqp$contentType=text/xml). 
> The method in question uses reflection to find a matching method name from the AMQP.BasicProperties class, and tries to populate accordingly.
> This works fine for all properties that take a String argument - however there are some that don't (specifically, headers takes a Map<String, Object>, deliveryMode and priority take Integer, and timestamp takes a Date), and it is impossible to populate these values because the invocation assumes a String is required, and fails on line 210.
> Whatsmore, the comment underneath (line 215) states that "this should really never happen since it should be caught by the above IF" - however the author of the code mustn't have tested all cases because this error is consistently present when trying to forward flow attributes in over a quarter of the available amqp properties.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)