[jira] [Commented] (NIFI-3442) FTPTransfer tries to evaluate PORT as expression language, although property doesn't support EL

Wed, 08 Mar 2017 21:01:18 -0800 

    [ 
https://issues.apache.org/jira/browse/NIFI-3442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15902494#comment-15902494
 ] 

ASF GitHub Bot commented on NIFI-3442:
--------------------------------------

Github user alopresto commented on the issue:

    https://github.com/apache/nifi/pull/1474
  
    I verified contrib-check, ran the tests (as mentioned, one failed but I 
resolved it), and built the project. I made a sample flow which generated a 
flowfile, updated a `username` attribute with "anonymous", and then used a 
`PutFTP` processor with the **username** value having the expression 
`${username}`. This worked successfully. 
    
    +1, merging. 
    ![screen shot 2017-03-08 at 8 48 23 
pm](https://cloud.githubusercontent.com/assets/798465/23736589/284dd634-0442-11e7-8424-6a4330aad443.png)
    ![screen shot 2017-03-08 at 8 48 08 
pm](https://cloud.githubusercontent.com/assets/798465/23736590/284e4b0a-0442-11e7-943f-412d152c4a20.png)
    



> FTPTransfer tries to evaluate PORT as expression language, although property 
> doesn't support EL
> -----------------------------------------------------------------------------------------------
>
>                 Key: NIFI-3442
>                 URL: https://issues.apache.org/jira/browse/NIFI-3442
>             Project: Apache NiFi
>          Issue Type: Bug
>    Affects Versions: 0.7.1, 1.1.1
>            Reporter: Andre F de Miranda
>            Assignee: Andre F de Miranda
>
> while crafting test coverage for PutFTP I noticed the following error:
> java.lang.AssertionError: java.lang.IllegalStateException: Attempting to 
> Evaluate Expressions but PropertyDescriptor[Port] indicates that the 
> Expression Language is not supported. If you realize that this is the case 
> and do not want this error to occur, it can be disabled by calling 
> TestRunner.setValidateExpressionUsage(false)
> Root cause seems to be a disconnect between the property builder (EL = false) 
> and the attempt  to evaluate the property as part of client.connect



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to