reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia Wang (QIUHE)" <Qiuhe.W...@microsoft.com.INVALID>
Subject RE: Uri Issues in REEF.NET IO
Date Thu, 08 Mar 2018 20:57:54 GMT
Are you talking about uri prefix used by file system? 

We have defined named parameter FileSysteUrl in both .Net and Java to allow the client to
specify the file system uri prefix you are using through configuration. If not defined, REEF
client gets default from the environment at runtime. Each FileSystem implementation can also
define its own way to get the file system uri prefix.

-- Julia

-----Original Message-----
From: Shouheng Yi [mailto:shouyi@microsoft.com.INVALID] 
Sent: Thursday, March 8, 2018 12:20 PM
To: dev@reef.apache.org
Subject: RE: Uri Issues in REEF.NET IO

A valid HDFS path. Sorry for the confusion.

Best,
Shouheng

-----Original Message-----
From: Markus Weimer [mailto:markus@weimo.de]
Sent: Thursday, March 8, 2018 11:35 AM
To: REEF Developers Mailinglist <dev@reef.apache.org>
Subject: Re: Uri Issues in REEF.NET IO

On Thu, Mar 8, 2018 at 9:57 AM, Shouheng Yi <shouyi@microsoft.com.invalid>
wrote:

>  proposed another fix to use Uri.OriginalString instead of 
> Uri.AbsolutePath. However the downside is that we lose 
> canonicalization of the Uri. Do we care about that? Who should bear 
> the responsibility of providing a valid HDFS, user or REEF?
>

What is a `valid HDFS`?

Thanks,

Markus
Mime
View raw message