On Mon, Sep 13, 2010 at 1:04 PM, Owen O'Malley wrote:
> On Mon, Sep 13, 2010 at 11:10 AM, Todd Lipcon wrote:
> > Yep, but there are plenty of 10 node clusters out there that do important
> > work at small startups or single-use-case installations, too. We need to
> > provide scalability and secu
On Mon, Sep 13, 2010 at 11:10 AM, Todd Lipcon wrote:
> Yep, but there are plenty of 10 node clusters out there that do important
> work at small startups or single-use-case installations, too. We need to
> provide scalability and security features that work for the 100+ node
> clusters but also no
On Mon, Sep 13, 2010 at 10:59 AM, Owen O'Malley wrote:
> On Mon, Sep 13, 2010 at 10:05 AM, Todd Lipcon wrote:
>
> > This is not MR-specific, since the strangely named hadoop.job.ugi
> determines
> > HDFS permissions as well.
>
> Yeah, after I hit send, I realized that I should have used common-d
On Mon, Sep 13, 2010 at 10:05 AM, Todd Lipcon wrote:
> This is not MR-specific, since the strangely named hadoop.job.ugi determines
> HDFS permissions as well.
Yeah, after I hit send, I realized that I should have used common-dev.
This is really a dev issue.
> "or the user must write a custom g
On Sep 13, 2010, at 10:05 AM, Todd Lipcon wrote:
> On Mon, Sep 13, 2010 at 9:31 AM, Owen O'Malley wrote:
>
>> Moving the discussion over to the more appropriate mapreduce-dev.
>>
>
> This is not MR-specific, since the strangely named hadoop.job.ugi determines
> HDFS permissions as well. +CC h
On Mon, Sep 13, 2010 at 9:31 AM, Owen O'Malley wrote:
> Moving the discussion over to the more appropriate mapreduce-dev.
>
This is not MR-specific, since the strangely named hadoop.job.ugi determines
HDFS permissions as well. +CC hdfs-dev... though I actually think this is an
issue that users w
