[
https://issues.apache.org/jira/browse/HADOOP-10775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated HADOOP-10775:
------------------------------------
Attachment: HADOOP-10775-009.patch
Patch 009; a bit of a simplification
As {{getWindowsPath()}} RTEs if there's no valid path, and {{getWindowsFile()}}
gives the file value or an FNFE, there's no need for a
{{getWindowsPathStrict()}}; it just complicates things.
Moved back to {{getWindowsPath()}} everywhere, except when an IOE was really
wanted —and there I use {{getWindowsFile().getCanonicalPath()}}
> Shell operations to fail with meaningful errors on windows if winutils.exe
> not found
> ------------------------------------------------------------------------------------
>
> Key: HADOOP-10775
> URL: https://issues.apache.org/jira/browse/HADOOP-10775
> Project: Hadoop Common
> Issue Type: Improvement
> Components: util
> Affects Versions: trunk-win, 2.7.1
> Environment: windows
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Priority: Minor
> Attachments: HADOOP-10775-002.patch, HADOOP-10775-003.patch,
> HADOOP-10775-004.patch, HADOOP-10775-005.patch, HADOOP-10775-006.patch,
> HADOOP-10775-007.patch, HADOOP-10775-008.patch, HADOOP-10775-009.patch,
> HADOOP-10775.patch
>
>
> If {{winutils.exe}} can't be found {{HADOOP_HOME}} wrong/unset or other
> causes, then an error is logged -but when any of the {{Shell}} operations are
> used, an NPE is raised rather than something meaningful.
> The error message at setup time should be preserved and then raised before
> any attempt to invoke a winutils-driven process made
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
