[ https://issues.apache.org/jira/browse/NIFI-7172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy LoPresto updated NIFI-7172: -------------------------------- Description: Many users have complained about the difficulty 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. was: 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. > 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 difficulty 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)