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

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

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

NIFI-2407 Implements EL support on some properties of processors/services
 - Added EL support to "Directory" property of ListHDFS and GetHDFS processors
 - Added EL support to "Destination" property for ConsumeJMS and PublishJMS 
processors
 - Added EL support to "MQ ConnectionFactory Implementation", "MQ client 
library path", "Broker URI" properties for the JMS Connection Factory Provider
 - Added EL support to "Database Connection URL", "Database Driver Class Name", 
"DB Driver jar url", "DB username", and "DB password" properties for the DBCP 
Connection Pool
 - Removed NotificationServiceManagerSpec.groovy, previous PR from Joe Witt 
covers the needed testing for Variable Registry/Value Lookup at this time
This closes #778.


> Add EL support to processors/controller services
> ------------------------------------------------
>
>                 Key: NIFI-2407
>                 URL: https://issues.apache.org/jira/browse/NIFI-2407
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>            Reporter: Jeff Storck
>            Assignee: Jeff Storck
>             Fix For: 1.0.0
>
>
> Add support for EL:
> * "Directory" property for GetHDFS and ListHDFS processors
> * "Destination Name" property for ConsumeJMS and PublishJMS processors
> * "MQ ConnectionFactory Implementation", "MQ client library path", "Broker 
> URI" properties for the JMS Connection Factory Provider
> * "Database Connection URL", "Database Driver Class Name", "DB Driver jar 
> url", "DB username", and "DB password" properties for the DBCP Connection Pool



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

Reply via email to