[
https://issues.apache.org/jira/browse/FALCON-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13876542#comment-13876542
]
Venkatesh Seetharam commented on FALCON-257:
--------------------------------------------
What I wanted to achieve is:
{code}path='project/falcon/raw_logs'{code}
translated to
{code}path='/home/$user/project/falcon/raw_logs'{code}
Latter is done by FileSystem. This is not possible since Oozie sends it as a
FQP.
{code}path='hdfs://host:8020/project/falcon/raw_logs'{code}
FileSystem does not view this as a relative path now.
> 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)
