[
https://issues.apache.org/jira/browse/FALCON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13871726#comment-13871726
]
Venkatesh Seetharam commented on FALCON-257:
--------------------------------------------
Good question. I wanted it to be relative paths as is done in
org.apache.hadoop.fs.FileSystem#getHomeDirectory.
{code}
public Path getHomeDirectory() {
return new Path("/user/"+System.getProperty("user.name"))
.makeQualified(this);
}
{code}
As I said in [#comment-13868677], this is not possible with Oozie since it
ALWAYS prefixes ${nameNode} to a Path and does not let the underlying FS to
interpret it.
Thoughts?
> File system storage wont work with relative paths
> -------------------------------------------------
>
> Key: FALCON-257
> URL: https://issues.apache.org/jira/browse/FALCON-257
> Project: Falcon
> Issue Type: Bug
> Affects Versions: 0.4
> Reporter: Venkatesh Seetharam
> Assignee: Venkatesh Seetharam
> Priority: Critical
> Fix For: 0.5
>
> Attachments: FALCON-257.patch
>
>
> I think I introduced this in FALCON-85. I was testing with relative URLs in
> feed and process definitions and it started failing with malformed URI.
> Workflow failed, error message[IOException: E0902: Exception occured:
> [Incomplete HDFS URI, no host:
> hdfs://venkatesh-secure-falcon-1.cs1cloud.internal:8020falcon/demo/apps/ingest/fs
> This is a simple line change:
> {code}
> return storageUrl + new Path(locationForType.getPath());
> {code}
> to
> {code}
> return new Path(storageUrl + "/" +
> locationForType.getPath()).toString();
> {code}
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
