[
https://issues.apache.org/jira/browse/NIFI-1832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15266471#comment-15266471
]
Pierre Villard commented on NIFI-1832:
--------------------------------------
[~joewitt] I agree, I think that with an upstream RouteOnAttribute processor it
is possible to cover all the use cases (even if it can be onerous to duplicate
a processor just to change this value). What processor are you implementing
[~simonellistonball]?
> 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)
