[
https://issues.apache.org/jira/browse/NIFI-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17074028#comment-17074028
]
Andy LoPresto commented on NIFI-7172:
-------------------------------------
Also consider newline truncation:
{quote}
Chris Sampson 2 minutes ago
So this turned out to be because the file had been uploaded without line
endings, so it was 200MB of text on a single line - I'll not stress about a
parser not being able to read that!
Will still look at tuning the timeout settings though I think as not the first
time I've run into the UI connectivity issue
Andy LoPresto 1 minute ago
We have an improvement Jira to handle trailing space, we should also add
something about ensuring to truncate at a newline because I don’t believe we
have any possible properties which include a newline in a valid config value.
{quote}
> Trim leading and trailing space from nifi.properties values
> -----------------------------------------------------------
>
> Key: NIFI-7172
> URL: https://issues.apache.org/jira/browse/NIFI-7172
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Configuration, Configuration Management
> Affects Versions: 1.11.2
> Reporter: Andy LoPresto
> Priority: Major
> Labels: configuration
>
> Many users have complained about the difficult of diagnosing unexpected
> behavior when a {{nifi.properties}} value does not match the desired value
> perfectly. Many property accessors perform an exact string match, and
> leading/trailing spaces can cause this to fail silently. This is especially
> to diagnose because it is often not apparent in the text editors used to
> display the properties file or log messages.
> The property value should have both leading and trailing space trimmed before
> being consumed.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
