[ 
https://issues.apache.org/jira/browse/NIFI-431?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Payne updated NIFI-431:
----------------------------
    Attachment: 0002-NIFI-431-Updated-validators-to-use-new-isExpressionL.patch

> Update standard validators not to validate if Expression Language is present
> ----------------------------------------------------------------------------
>
>                 Key: NIFI-431
>                 URL: https://issues.apache.org/jira/browse/NIFI-431
>             Project: Apache NiFi
>          Issue Type: Sub-task
>          Components: Extensions, Tools and Build
>            Reporter: Mark Payne
>             Fix For: 0.1.0
>
>         Attachments: 
> 0002-NIFI-431-Updated-validators-to-use-new-isExpressionL.patch
>
>
> We should not validate input in validators if expression language is used. 
> This way, we can avoid having to set property validators to NonEmptyValidator 
> and instead use more legit validators like PositiveIntegerValidator. This 
> way, if an Expression is used, the validator should indicate that the 
> property is valid. Otherwise, it should perform the validation.
> This provides two very big benefits to users: 
> * If the user enters an invalid expression such as "${myVar" (without the 
> closing brace) this is valid according to the NonEmptyValidator. Assigning a 
> more legitimate validator such as a PositiveIntegerValidator will detect that 
> this is not an expression and will mark it as invalid.
> * If no expression is used, we can still get the benefits of validation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to