[
https://issues.apache.org/jira/browse/NIFI-430?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376509#comment-14376509
]
ASF subversion and git services commented on NIFI-430:
------------------------------------------------------
Commit 2429e0540fcce90bfd2ced450d4cd124cff3a6b4 in incubator-nifi's branch
refs/heads/develop from [~markap14]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;h=2429e05 ]
NIFI-430: Added isExpressionLanguageSupported and isExpressionLanguagePresent
methods to ValidationContext
> NiFi API needs to provide an isExpressionLanguagePresent() method to
> validators
> -------------------------------------------------------------------------------
>
> Key: NIFI-430
> URL: https://issues.apache.org/jira/browse/NIFI-430
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework, Extensions
> Reporter: Mark Payne
> Fix For: 0.1.0
>
> Attachments:
> 0001-NIFI-430-Added-isExpressionLanguageSupported-and-isE.patch
>
>
> Currently, validators have no way of determining whether or not a property
> value contains an Expression Language Expression. This ends up requiring
> processor developers to write code like
> https://github.com/apache/incubator-nifi/pull/36.patch, in which they have to
> check for presence of characters in the value. The onus of this should be on
> the framework.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
