[
https://issues.apache.org/jira/browse/FALCON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13922061#comment-13922061
]
Shwetha G S commented on FALCON-257:
------------------------------------
Why not use path.makeQualified()? It already takes care of handling
absolute/relative paths
With this patch, if the relative path is used in feed location, feed retention,
replication and process will work fine, right? We should also check if relative
paths work for process workflow and lib path.
> 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-v1.patch, 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.2#6252)
