[jira] [Commented] (NIFI-5937) PutElasticsearchHttpRecord uses system default encoding

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on NIFI-5937:
-------------------------------------------------------

Commit 1a443c73ecb0ed00233b66d282031aa5b37afb24 in nifi's branch refs/heads/master from Alex Savitsky
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=1a443c7 ]

NIFI-5937 use processor-configured encoding instead of the system default

NIFI-5937 added tests to verify that accented characters are preserved correctly

NIFI-5937 unfolding starred imports

NIFI-5937 unfolding starred imports (now with statics)

Signed-off-by: Ed <ed...@gmail.com>

This closes #3250


> PutElasticsearchHttpRecord uses system default encoding
> -------------------------------------------------------
>
>                 Key: NIFI-5937
>                 URL: https://issues.apache.org/jira/browse/NIFI-5937
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Extensions
>    Affects Versions: 1.8.0
>            Reporter: Alex Savitsky
>            Assignee: Alex Savitsky
>            Priority: Major
>          Time Spent: 1h 20m
>  Remaining Estimate: 0h
>
> PutElasticsearchHttpRecord line 348:
> {code:java}
> json.append(out.toString());
> {code}
> This results in the conversion being done using system default encoding, possibly garbling non-ASCII characters in the output. Should use the encoding configured in the processor in the toString call.
> As a workaround, the "file.encoding" system property can be specified explicitly in the bootstrap.conf:
> {code:java}
> java.arg.7=-Dfile.encoding=UTF-8{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)