Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-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 E75F110659 for ; Fri, 31 May 2013 17:04:24 +0000 (UTC) Received: (qmail 32971 invoked by uid 500); 31 May 2013 17:04:20 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 32810 invoked by uid 500); 31 May 2013 17:04:19 -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 32785 invoked by uid 99); 31 May 2013 17:04:19 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 17:04:19 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of harsh@cloudera.com designates 209.85.192.180 as permitted sender) Received: from [209.85.192.180] (HELO mail-pd0-f180.google.com) (209.85.192.180) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 31 May 2013 17:04:12 +0000 Received: by mail-pd0-f180.google.com with SMTP id 14so2509613pdc.11 for ; Fri, 31 May 2013 10:03:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=HktJctaBjvj/Qu8QJdWWDlLRjYpEcn6H2ZRb2ybHf+4=; b=DmzP6kXJqB9AYAfffA+miKRcfPO4V+KCkyQRuHL5Aet8TwZc5178ctX3Hvm//g/wq0 ddVXAgGAM8jXEMQMhMENeXZJCn1uWY78qc3NzSX7wNiz+X6yQF06JzPJyFHeozy2TwFE H8yhYiRfqkigRWkV/ICLyTM2+eyP46YaJuiv8qHu/8KCNEUlYfwd/FhlKSpyxf22trUN uTdL++9tiB48apyBlqBKzTxQii0fsSLS35lnAS6zGRfjNhJBLe0oqQRnFQ44iDcC5rMA 6bEbSxpZ0oy/MYYSRahJ0XEGMpFZA0sa/jDUaYcHYcunK1wFY/LcF+ClJj3EHT9agrDV JWPA== X-Received: by 10.66.163.200 with SMTP id yk8mr14400471pab.170.1370019831451; Fri, 31 May 2013 10:03:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.77.230 with HTTP; Fri, 31 May 2013 10:03:31 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Fri, 31 May 2013 22:33:31 +0530 Message-ID: Subject: Re: possible to change replication factor at file creation time (with copyFromLocal)? To: "" Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQnjmdIwvEwJ5QKq6g8MARP4EMqVmeC80O6nnQhyixoq4PYDidSC0BVC+3CCesp0S+1UhJZS X-Virus-Checked: Checked by ClamAV on apache.org Hi Julian, Yes, "dfs" subcommand accepts config overrides via -D. Just do "hadoop dfs -Ddfs.replication=3DX -copyFromLocal =85". On Fri, May 31, 2013 at 10:27 PM, Julian Bui wrote: > Hi hadoop users, > > I am aware that you can set the replication factor of a file after it's b= een > created, but can you do it as you copy files to the HDFS? My hope/intuit= ion > is that if you were able to reduce the replication factor of a file while > copying, the copy time would decrease. I'm finding it difficult waiting = for > large data sets to copy over. > > I am currently doing: > > hadoop dfs -copyFromLocal "/copy/from/path/" input > > and am wondering if it's possible to also specify something like -setrep = on > the same line. -setsrep requires you to specify the file, which implies > that it has to exist first, requiring two separate commands. > > Thanks in advance, > -Julian --=20 Harsh J