Skip to content

Conversation

@thadguidry
Copy link
Contributor

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 everything 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.

Giving this extra hint for Windows users is an easier workaround for now 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 and providing workarounds.

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.

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 everything 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.

Giving this extra hint for Windows users is an easier workaround for now 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 and providing workarounds.

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.
@joewitt
Copy link
Contributor

joewitt commented Jan 25, 2016

Hello - can you create a JIRA for this contrib and we can track/discuss there.

Thanks!

@thadguidry
Copy link
Contributor Author

@thadguidry thadguidry closed this Jan 25, 2016
@joewitt
Copy link
Contributor

joewitt commented Jan 25, 2016

thank you. We're digging in hard for the 050 release now so response time on this might be a bit slow. Thanks for contributing!

mattyb149 pushed a commit to mattyb149/nifi that referenced this pull request Dec 9, 2020
This closes apache#181

Signed-off-by: Aldrin Piri <aldrin@apache.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants