[
https://issues.apache.org/jira/browse/NIFI-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16071863#comment-16071863
]
Joseph Witt commented on NIFI-3931:
-----------------------------------
[~pvillard] I dont think it is this PR that caused it but I do suspect this
processor now has a pretty important bug. By enabling expression language
support, and on a per flowfile basis, i dont think we're handling connections
properly now. What if there are multiple threads sending flowfiles and each
wants a different host/port/server/password/etc.. Are we setting up/tearing
down those properly? This processor did not enable expression language or at
the very least didn't have it support flowfile seeded expression language
because the connection handling/efficiency would require a good bit of work.
I've not personally confirmed this suspicion yet so I could be wrong. But we
should definitely look into that.
> putSftp process port property should support for expression language
> --------------------------------------------------------------------
>
> Key: NIFI-3931
> URL: https://issues.apache.org/jira/browse/NIFI-3931
> Project: Apache NiFi
> Issue Type: Improvement
> Affects Versions: 1.2.0
> Reporter: Cheng Chin Tat
> Assignee: Pierre Villard
> Priority: Minor
> Labels: easyfix
>
> PutSftp Processor port property should support for expression language so
> that dynamic port number can be pass to the processor during run time.
> Rather than preset the port on design time.
> This changes involve changing the PropertyDescriptor SFTP_PORT validator
> StandardValidators.NON_NEGATIVE_INTEGER_VALIDATOR to
> StandardValidators.NON_EMPTY_VALIDATOR and other codes.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
