Thad Guidry created NIFI-1437:
---------------------------------
Summary: CharacterSetConversion and other Processors do not handle
Windows paths well enough.
Key: NIFI-1437
URL: https://issues.apache.org/jira/browse/NIFI-1437
Project: Apache NiFi
Issue Type: Bug
Components: Core Framework
Environment: Windows 7 64bit Enterprise, Windows 10 64bit Professional
Reporter: Thad Guidry
Priority: Minor
Windows users typically don't have to worry about supplying a trailing
slash....until they work with some Java programs like Nifi.
An input path such as
"E:\git\nifi\nifi-nar-bundles\nifi-standard-bundle\nifi-standard-processors\src\test\resources\CharacterSetConversionSamples\TestInput"
that does not have a trailing slash will cause NiFi to parse all files in
CharacterSetConversionSamples....not the TestInput folder. To remedy the
situation, Windows users just need to add the trailing slash \ such as
"E:\git\nifi\nifi-nar-bundles\nifi-standard-bundle\nifi-standard-processors\src\test\resources\CharacterSetConversionSamples\TestInput\"
and then NiFi is able to use the correct path and not pickup extra files from
the unexpected parent folder of CharacterSetConversionSamples.
Giving an extra hint for Windows users is sometimes an easier workaround than
doing Windows OS detection with
http://commons.apache.org/proper/commons-lang/javadocs/api-release/org/apache/commons/lang3/SystemUtils.html#IS_OS_WINDOWS
I think most Windows users and developers are aware of this kind of issue that
we deal with everyday, and the extra hint should be enough...
but others might disagree and want to fix Processor path issues for Windows
users in the core framework itself.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
