GitHub user jtstorck opened a pull request:
https://github.com/apache/nifi/pull/778
NIFI-2407 Implements EL support on some properties of processors/servâ¦
â¦ices
- 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
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jtstorck/nifi NIFI-2407
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/778.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #778
----
commit 1461686aae468cf12878d8beb7da84db5218d917
Author: Jeff Storck <[email protected]>
Date: 2016-07-27T15:51:15Z
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
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---