You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "Peter Turcsanyi (Jira)" <ji...@apache.org> on 2026/05/27 13:15:00 UTC
[jira] [Resolved] (NIFI-15977) PutSmbFile does not support non-default ports
[ https://issues.apache.org/jira/browse/NIFI-15977?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Peter Turcsanyi resolved NIFI-15977.
------------------------------------
Fix Version/s: 2.10.0
Resolution: Fixed
> PutSmbFile does not support non-default ports
> ---------------------------------------------
>
> Key: NIFI-15977
> URL: https://issues.apache.org/jira/browse/NIFI-15977
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Jakub Bogusz
> Assignee: Jakub Bogusz
> Priority: Major
> Fix For: 2.10.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> PutSmbFile & GetSmbFile processors don't expose a property to use a port different than the default. This is not an issue for GetSmbFile, as it's pretty much replaced by ListSmb and FetchSmb and those use SmbjClientProviderService which has a configurable port. But the PutSmbFile has no such alternative.
> It seems it would be hard to migrate PutSmbFile to use the new service in a non-breaking way. Maybe some "Connection Strategy" could switch between the old, processor-managed client and a new client service? Or maybe just a new version of "put" processor would make sense?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)