[
https://issues.apache.org/jira/browse/NIFI-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266454#comment-15266454
]
Joseph Witt commented on NIFI-1832:
-----------------------------------
[~pvillard] [~simonellistonball] For background: The concept of allowable
values and expression language was never really meant to work together. The
'allowable values' construct was so that we could nicely support an enumerate
set of values that were carried through/available through the REST API and UI
to constrain what a user could choose. The concept of expression language came
around after. I think we just never blocked the usage of them together. I am
inclined to think we should not allow them to be used together but perhaps I'm
missing a use case or concept.
> Testing EL properties with AllowableValues
> ------------------------------------------
>
> Key: NIFI-1832
> URL: https://issues.apache.org/jira/browse/NIFI-1832
> Project: Apache NiFi
> Issue Type: Bug
> Components: Tools and Build
> Affects Versions: 0.6.1
> Environment: Testing
> Reporter: Simon Elliston Ball
> Assignee: Pierre Villard
> Priority: Minor
>
> I’ve come across an interesting problem with MockFlowFile while testing a
> custom processor. My property has an AllowableValue list, and supports
> expression language. The test uses:
> runner.setProperty(PROPERTY_REF, "${attribute.name}”);
> However, the test fails on validation of in the MockFlowFile with the
> unevaluated version of the EL invalid against the allowed values list.
> 'Property' validated against '${attribute.name}' is invalid because Given
> value is not found in allowed set ...
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
