GitHub user pvillard31 opened a pull request:
https://github.com/apache/nifi/pull/401
NIFI-1832 Allowing expression language in properties with a set of
allowable values
At the moment, if a property is defined with a set of allowable values AND
is supporting expression language, then validation will always fail when the
expression language value is not matching an allowable value. There are two
options:
- In the processor, add in the allowable values the expression language
value that is authorized and let the user knows that the expected value MUST BE
in this specific attribute.
Example: .allowableValues("A", "B", "C", "${myProcessor.type}")
Then the incoming flow files must have this attribute (using
UpdateAttribute before).
- Authorize any input value when expression language is supported for this
kind of properties.
This PR is a proposition for the second option.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/pvillard31/nifi NIFI-1832
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/401.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #401
----
commit de320a6e9e1370964783016538fe07aa1ae6cb17
Author: Pierre Villard <pierre.villard...@gmail.com>
Date: 2016-05-02T09:57:28Z
NIFI-1832 Allowing expression language in properties with a set of
allowable values
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
