Your architecture is a bit unusual in that you seem to be proposing that
users get direct access to the hadoop storage layer.
More common is to have a controller layer that mediates requests to store or
read data.
With that layer of abstraction, you can deal with some of the problems
associated w
Hi,
thank you both for the links and advices. Looking at the work in progress
concerning security, it seems that currently the only way to have
authentication is to implement it at the Web Server level. In my case, my
web server is deployed under Tomcat, therefore I think I should manage
clients au
Also, you can look at work in progress:
http://issues.apache.org/jira/browse/HADOOP-4487
thanks,
dhruba
On Wed, Jul 22, 2009 at 9:11 AM, Andrey Pankov wrote:
> Maybe this would be interesting for you,
>
>
> http://www.hadoop.iponweb.net/Home/hdfs-over-webdav/authentication-and-permissions
>
> O
Maybe this would be interesting for you,
http://www.hadoop.iponweb.net/Home/hdfs-over-webdav/authentication-and-permissions
On Wed, Jul 22, 2009 at 19:00, Giovanni Tusa wrote:
> Hi all,
>
> on my company we recently began some projects where we would like to
> actively use hadoop.
> For one of th
Hi all,
on my company we recently began some projects where we would like to
actively use hadoop.
For one of them, basically we have implemented a feed service where feed
entries (there could be a lot of data because many different users can post
feeds), are actually stored in the server filesyste
