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

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

Github user YolandaMDavis commented on the issue:

    https://github.com/apache/nifi/pull/1957
  
    Ran tests using FileZilla on Windows 10 Server with flow containing GetFTP 
-> UpdateAttributes (for filename append) -> PutFTP.  Worked as expected with 
the below use cases:
    
    Below demonstrates cases where UTF-8 was disabled then enabled
    
    
![image](https://user-images.githubusercontent.com/1371858/27655615-fa8e1c02-5c13-11e7-8728-cd327bc8cf04.png)
    
    Files were stored as expected on FTP server:
    
    
![image](https://user-images.githubusercontent.com/1371858/27655598-ec13d52c-5c13-11e7-94c6-16b87a65637c.png)
    
    +1  will merge shortly



> Add UTF8 support for GetFTP and PutFTP
> --------------------------------------
>
>                 Key: NIFI-4137
>                 URL: https://issues.apache.org/jira/browse/NIFI-4137
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>            Reporter: Matt Burgess
>            Assignee: Matt Burgess
>
> When using GetFTP or PutFTP, the filename is not properly handled by NiFi if 
> it contains special characters like é, è, à, ...
> [RFC-2640|http://filezilla-project.org/specs/rfc2640.txt] is an extension of 
> the FTP protocol to handle non-English characters (source: 
> https://wiki.filezilla-project.org/Character_Encoding). The client and server 
> must both support UTF-8.
> This Jira proposes to add a property for "Use UTF-8 Encoding", defaulted to 
> false to maintain existing behavior. When set to true, 
> setControlEncoding("UTF-8") should be called on the client.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to