Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 30B6DE8DB for ; Tue, 29 Jan 2013 23:17:30 +0000 (UTC) Received: (qmail 54407 invoked by uid 500); 29 Jan 2013 23:17:25 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 54307 invoked by uid 500); 29 Jan 2013 23:17:25 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 54299 invoked by uid 99); 29 Jan 2013 23:17:25 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 23:17:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of michael@cloudera.com designates 209.85.212.177 as permitted sender) Received: from [209.85.212.177] (HELO mail-wi0-f177.google.com) (209.85.212.177) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 Jan 2013 23:17:20 +0000 Received: by mail-wi0-f177.google.com with SMTP id hm14so988484wib.4 for ; Tue, 29 Jan 2013 15:16:59 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=/q8nC/2ekq+u4js1WBWqduOMgZZ8S8O3bJ34+/5UIdE=; b=ArXuIxkVIMd4XAR1QmInn9Dx/7h4SFKbn3xT9vH2/P5Kv3qdRdu7M4r67leqitpRgJ HusSPYjgo//532J6J8p1N/hauoOchaXV/UvsP20AupB66f12/KMs7YaR+4x93H7A7b1V g1LnAsIxZ9mcD+MBIxRqNPb0JBVG5rPIHzANk4JrgAhptjRv1XW+o3aLCnVpNpZE4KX1 +TB5xHQ1rJdg0x56aMm3JvPVNp1Q7FMz7AR9FzNyGLs5CGeIpnCveRMN3aIqqp1vbyDE avMtfIfqQUaWTr3YzwJ6jrxkMJ2xJy0xLRU+HDRxazHr0etDdHVbq5FitWJ2f3Vsqk1a 0Ybg== X-Received: by 10.194.78.207 with SMTP id d15mr5241519wjx.52.1359501419122; Tue, 29 Jan 2013 15:16:59 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.109.8 with HTTP; Tue, 29 Jan 2013 15:16:37 -0800 (PST) In-Reply-To: <04D4975F-B4B6-4110-955A-66B79ECF50C9@nice.com> References: <168E62EA-05ED-48B9-99CE-5050725AE5E6@nice.com> <04D4975F-B4B6-4110-955A-66B79ECF50C9@nice.com> From: Michael Katzenellenbogen Date: Tue, 29 Jan 2013 18:16:37 -0500 Message-ID: Subject: Re: Initial Permission Settings To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bfcf91a288fda04d4759730 X-Gm-Message-State: ALoCoQk44fMDUm7Sim3TY8VHQWbBMaOfliDCrPdtXl79J1791ayMgvlyuyG3OK2AdKAnQz88qtVj X-Virus-Checked: Checked by ClamAV on apache.org --047d7bfcf91a288fda04d4759730 Content-Type: text/plain; charset=ISO-8859-1 dfs.umask has been deprecated in favor of dfs.umaskmode Typically a umask is represented as an octal, whereas dfs.umask was represented as a decimal. dfs.umaskmode accepts octal notation, as is preferred. For details, feel free to read up on https://issues.apache.org/jira/browse/HADOOP-6234 -Michael On Tue, Jan 29, 2013 at 5:47 PM, Serge Blazhiyevskyy < Serge.Blazhiyevskyy@nice.com> wrote: > Thanks for response. > > > I am still a bit confused. > > There are two parameters: dfs.umask and dfs.umaskmode and both of them > seems to be deprecated in different hadoop versions. > > Does anybody know whats going on with those two parameters? > > > Thanks > Serge > > > > > On Jan 29, 2013, at 12:10 PM, Vinod Kumar Vavilapalli < > vinodkv@hortonworks.com> wrote: > > > Please check your dfs umask (dfs.umask configuration property). > > HTH, > +Vinod > > > On Tue, Jan 29, 2013 at 12:02 PM, Serge Blazhiyevskyy < > Serge.Blazhiyevskyy@nice.com> wrote: > Hi all, > > Quick question about hadoop dfs -put local_file hdfs_file command > > > It seems that regardless of permissions for local_file the initial > permissions for hdfs_file are -rw-r--r--, which allow file to be read by > other users. > > Is there are way to change the initial file settings? > > Thanks in advance. > Serge > > > > > > -- > +Vinod > Hortonworks Inc. > http://hortonworks.com/ > > --047d7bfcf91a288fda04d4759730 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable dfs.umask has been deprecated in favor of dfs.umaskmode

= Typically a umask is represented as an octal, whereas dfs.umask was represe= nted as a decimal. dfs.umaskmode accepts octal notation, as is preferred. F= or details, feel free to read up on=A0https://issues.apache.org/jira/browse/HADOOP-6234<= /a>

-Michael

On Tue, Jan = 29, 2013 at 5:47 PM, Serge Blazhiyevskyy <Serge.Blazhiyevskyy@n= ice.com> wrote:
Thanks for response.


I am still a bit confused.

There are two parameters: dfs.umask and dfs.umaskmode and both of them seem= s to be deprecated in different hadoop versions.

Does anybody know whats going on with those two parameters?


Thanks
Serge




On Jan 29, 2013, at 12:10 PM, Vinod Kumar Vavilapalli <vinodkv@hortonworks.com<mailto:vinodkv@hortonworks.com>> wrote:<= br>

Please check your dfs umask (dfs.umask configuration property).

HTH,
+Vinod


On Tue, Jan 29, 2013 at 12:02= PM, Serge Blazhiyevskyy <Serge.Blazhiyevskyy@nice.com<mailto:Serge.Blazhiyevskyy@nice.com>> wrote:
Hi all,

Quick question about hadoop dfs -put local_file hdfs_file command


It seems that regardless of permissions for local_file the initial permissi= ons for hdfs_file are -rw-r--r--, which allow file to be read by other user= s.

Is there are way to change the initial file settings?

Thanks in advance.
Serge





--
+Vinod
Hortonworks Inc.
http://hortonworks.co= m/


--047d7bfcf91a288fda04d4759730--