Marek Kovar created NIFI-3590:
---------------------------------

             Summary: FetchSFTP Move Completion Strategy Remote Host Properties
                 Key: NIFI-3590
                 URL: https://issues.apache.org/jira/browse/NIFI-3590
             Project: Apache NiFi
          Issue Type: Bug
          Components: Extensions
    Affects Versions: 1.1.1
         Environment: Debian Wheezy, jdk1.8
            Reporter: Marek Kovar


There is an problem to use Move Completion strategy with remote host defined 
using Expression Language.

Eg. Port number defined using Expression language (${sftp.remote.port}) is fine 
for the fetch itself, but for the file renaming it's causing following error:
{quote}
2017-03-13 15:58:06,181 ERROR [Timer-Driven Process Thread-6] 
o.a.nifi.processors.standard.FetchSFTP
java.lang.NumberFormatException: For input string: ""
        at 
java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) 
~[na:1.8.0_111]
        at java.lang.Integer.parseInt(Integer.java:592) ~[na:1.8.0_111]
        at java.lang.Integer.parseInt(Integer.java:615) ~[na:1.8.0_111]
        at 
org.apache.nifi.attribute.expression.language.StandardPropertyValue.asInteger(StandardPropertyValue.java:78)
 ~[nifi-expression-language-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.processors.standard.util.SFTPTransfer.getChannel(SFTPTransfer.java:400)
 ~[nifi-standard-processors-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.processors.standard.util.SFTPTransfer.rename(SFTPTransfer.java:608)
 ~[nifi-standard-processors-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.processors.standard.FetchFileTransfer.onTrigger(FetchFileTransfer.java:316)
 ~[nifi-standard-processors-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.processor.AbstractProcessor.onTrigger(AbstractProcessor.java:27)
 ~[nifi-api-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.controller.StandardProcessorNode.onTrigger(StandardProcessorNode.java:1099)
 [nifi-framework-core-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:136)
 [nifi-framework-core-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.controller.tasks.ContinuallyRunProcessorTask.call(ContinuallyRunProcessorTask.java:47)
 [nifi-framework-core-1.1.2.jar:1.1.2]
        at 
org.apache.nifi.controller.scheduling.TimerDrivenSchedulingAgent$1.run(TimerDrivenSchedulingAgent.java:132)
 [nifi-framework-core-1.1.2.jar:1.1.2]
        at 
java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 
[na:1.8.0_111]
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 
[na:1.8.0_111]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
 [na:1.8.0_111]
        at 
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
 [na:1.8.0_111]
        at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
[na:1.8.0_111]
        at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
[na:1.8.0_111]
        at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111]
{quote}



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

Reply via email to