[
https://issues.apache.org/jira/browse/NIFI-4977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16414442#comment-16414442
]
ASF subversion and git services commented on NIFI-4977:
-------------------------------------------------------
Commit 56ad14ad1eb5bc1d716f6d2664618a07fd049e07 in nifi's branch
refs/heads/master from Joe Percivall
[ https://git-wip-us.apache.org/repos/asf?p=nifi.git;h=56ad14a ]
NIFI-4977 Adding expression language support to the Sender properties of
PutSyslog
This closes #2547.
Signed-off-by: Bryan Bende <[email protected]>
> PutSyslog should support Expression Language for it's Sender properties
> -----------------------------------------------------------------------
>
> Key: NIFI-4977
> URL: https://issues.apache.org/jira/browse/NIFI-4977
> Project: Apache NiFi
> Issue Type: Improvement
> Reporter: Joseph Percivall
> Assignee: Joseph Percivall
> Priority: Minor
> Fix For: 1.6.0
>
>
> As part of the continued effort to add access to the variable registry to
> processors, the PutSyslog processor should expose expression language to it's
> sender properties. These properties control where and how the processor sends
> to.
> This update should better align PutSyslog with the other PutX processors
> which support EL on the sender properties (Slack, TCP, UDP).
> These properties are not evaluated per FlowFile and shouldn't be expected to
> change between onTriggers (since the sender pool is shared) so it will need
> to be documented as such that the
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)