[
https://issues.apache.org/jira/browse/NIFI-2208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15392919#comment-15392919
]
ASF GitHub Bot commented on NIFI-2208:
--------------------------------------
Github user JPercivall commented on a diff in the pull request:
https://github.com/apache/nifi/pull/571#discussion_r72169945
--- Diff:
nifi-commons/nifi-expression-language/src/main/java/org/apache/nifi/attribute/expression/language/StandardPropertyValue.java
---
@@ -134,9 +139,14 @@ public PropertyValue
evaluateAttributeExpressions(final FlowFile flowFile, final
return this;
}
- return new
StandardPropertyValue(preparedQuery.evaluateExpressions(flowFile,
additionalAttributes, decorator), serviceLookup, null);
+ VariableRegistry sysRegistry = variableRegistry != null ?
variableRegistry : VariableRegistryUtils.createVariableRegistry();
--- End diff --
Is there any time this is designed to be null or is this just a fallback?
If it does get created here, it won't have the variables from the properties
values ingested by the FlowController.
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
