On 24 May 2013 01:28, Colin McCabe wrote:
> You might try looking at what KosmoFS (KFS) did. They have some code in
> org/apache/hadoop/fs which calls their own Java shim.
>
> This way, the shim code in hadoop-common gets updated whenever FileSystem
> changes, but there is no requirement to inst
> - Original Message -
> From: "Harsh J"
> To: common-dev@hadoop.apache.org
> Sent: Thursday, May 23, 2013 1:37:30 PM
> Subject: Re: [DISCUSS] - Committing client code to 3rd Party FileSystems
> within Hadoop Common
>
> I think we do a fairly good work maintai
: Thursday, May 23, 2013 1:37:30 PM
Subject: Re: [DISCUSS] - Committing client code to 3rd Party FileSystems within
Hadoop Common
I think we do a fairly good work maintaining a stable and public FileSystem
and FileContext API for third-party plugins to exist outside of Apache
Hadoop but still b
I think we do a fairly good work maintaining a stable and public FileSystem
and FileContext API for third-party plugins to exist outside of Apache
Hadoop but still be able to work well across versions.
The question of test pops up though, specifically that of testing against
trunk to catch regress
(Resending - I think the first time I sent this out it got lost within all the
ByLaws voting)
Hi Folks
My name is Steve Watt and I am presently working on enabling glusterfs to be
used as a Hadoop FileSystem. Most of the work thus far has involved developing
a Hadoop FileSystem plugin for glus
