[
https://issues.apache.org/jira/browse/NIFI-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joseph Witt updated NIFI-2208:
------------------------------
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...
was:
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.
In addition to the merge this should also include a fix to ensure that variable
registry is initialized on startup that variables from the registry are applied
during EL compilation based on the following order of precedence:
1) Flow File Attribute
2) Processor provided variables
3) User Defined Variables (via custom properties)
4) JVM System Properties
5) OS Environment Variables
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...
> Support Custom Properties in Expression Language - 1.x baseline
> ---------------------------------------------------------------
>
> Key: NIFI-2208
> URL: https://issues.apache.org/jira/browse/NIFI-2208
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Mark Payne
> Assignee: Yolanda M. Davis
> Priority: Blocker
> Fix For: 1.0.0
>
>
> 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...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
