[NIFI-2208] Support Custom Properties in Expression Language - 1.x baseline

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.0.0, 1.0.0-Beta
• Component/s: Core Framework
• Labels: documentation migration
• Assignee: Yolanda M. Davis
• Reporter: Mark Payne
• Created: 08/Jul/16 20:19
• Updated: 04/Aug/16 21:23
• Resolved: 01/Aug/16 18:20

Description

NIFI-1974 addressed this for the 0.x baseline but the PR does not apply cleanly to the 1.x baseline. Creating a separate JIRA for 1.x so that we can close out NIFI-1974 since 0.7.0 is ready to be released.

The VariableRegistry is:

• User defined properties
• System Properties (at startup)
• OS Environment Variables (at startup)

Then for substitution the values can be replaced using the following logic in the following order
1) Any supplied attribute maps (in order)
2) If flow file supplied then its properties
3) If flow file supplied then its attributes
4) Variable Registry (and its ordering as shown above).

Finally the following processor properties should be enabled to support expression language:

Put HDFS/Get HDFS/List HDFS

• Directory property

ConsumeJMS/PublishJMS

• Destination Name property

MS Connection Factory Provider
-MQ ConnectionFactory Implementation (fqn classname)
-MQ client library path
-Broker URI

DBCP Connection Pool:
-Database Connection URL
-Database Driver Class Name
-DB Driver jar url
-DB username
-DB password

ConvertCSVToAvro
-add EL support for the following property
-csv charset
-and below...

Issue Links

• relates to: NIFI-1974 Support Custom Properties in Expression Language
• links to: GitHub Pull Request #571
• links to: GitHub Pull Request #754