[
https://issues.apache.org/jira/browse/NIFI-5937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16738935#comment-16738935
]
ASF subversion and git services commented on NIFI-5937:
-------------------------------------------------------
Commit 3e52ae952d05867f3366dc4f796ae193a84b4b2c in nifi's branch
refs/heads/master from Alex Savitsky
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=3e52ae9 ]
NIFI-5909 added optional settings for date, time, and timestamp formats used to
write Records to Elasticsearch
NIFI-5909 added content checks to the unit tests
NIFI-5937 use explicit long value for test dates/times (to not depend on the
timezone of test executor)
NIFI-5937 tabs to spaces
Fixing checkstyle violations introduced by
https://github.com/apache/nifi/pull/3249 PR)
NIFI-5937 adjusted property descriptions for consistency; limited EL scope to
variable registry; added an appropriate validator along with its Maven
dependency; moved format initialization to @OnScheduled
NIFI-5909 tabs to spaces
Signed-off-by: Ed <[email protected]>
This closes #3227
> 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
> Fix For: 1.9.0
>
> Time Spent: 1h 40m
> 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)
