You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Joseph Witt (JIRA)" <ji...@apache.org> on 2017/12/24 15:38:02 UTC

[jira] [Commented] (NIFI-4723) PublishAMQP 1.4.0 support Expression Language

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

Joseph Witt commented on NIFI-4723:
-----------------------------------

[10:36 AM] Joe Witt: As your JIRA https://issues.apache.org/jira/browse/NIFI-4723 notes it isn't presently supported for those properties.  it is on some others.  But please note that enabling expression language needs to be done with care.  Doing it for env variables for example is fair game.  But doing it when expression language can take flowfiles is too specific as that could require a completely different connection management.  Consider the case where hostname or username or password were on a flowfile.  Also, expression language isn't suitable for sensitive values so password would not be recommended.
[10:37 AM] Joe Witt: With the upcoming Versioned Flow Registry (discussions to kick off the RC/Vote have started!) then this becomes far easier to manage as well.

COPYING hipchat comments here ^^

> PublishAMQP 1.4.0 support Expression Language 
> ----------------------------------------------
>
>                 Key: NIFI-4723
>                 URL: https://issues.apache.org/jira/browse/NIFI-4723
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Examples, Extensions
>            Reporter: bat-hen
>
> Hi,
> there is no support to Expression Language in PublishAMQP? for:
> Host Name
> Port
> User Name
> Password
> we want to do deployment with template and we cant use Expression Language in rabbitmq.:|



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)