[
https://issues.apache.org/jira/browse/OOZIE-919?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13422659#comment-13422659
]
Alejandro Abdelnur commented on OOZIE-919:
------------------------------------------
why not URI? it does all the right checks.
#c and #d, AFAIK, are not valid HDFS URIs, are they? and even in the case they
are, we cannot use them because then we could differentiate a relative path
(foo/bar) from a path with authority and no scheme (host/bar).
> Notify user correctly of NN and JT hostname validity
> ----------------------------------------------------
>
> Key: OOZIE-919
> URL: https://issues.apache.org/jira/browse/OOZIE-919
> Project: Oozie
> Issue Type: Improvement
> Components: core
> Affects Versions: trunk
> Reporter: Ashish Vaidya
> Priority: Minor
> Labels: validation
> Fix For: trunk
>
> Attachments: OOZIE-919.WIP.patch
>
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> When value provided for JT and/or NN is malformed (incorrect
> scheme://hostname:port syntax), we throw the following error:
> 'Jobtracker/namenode not in whitelist.'
> This is misleading to the user. We should let the user know that the input
> for those is malformed and the hostname:port syntax needs to be corrected.
> Above doesn't (and shouldn't) affect the tallying of those values against the
> respective white lists.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
