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 481C1D28F for ; Sat, 22 Dec 2012 18:54:33 +0000 (UTC) Received: (qmail 51769 invoked by uid 500); 22 Dec 2012 18:54:28 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 51642 invoked by uid 500); 22 Dec 2012 18:54:28 -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 51635 invoked by uid 99); 22 Dec 2012 18:54:28 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Dec 2012 18:54:28 +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 (nike.apache.org: domain of barak.yaish@gmail.com designates 209.85.216.45 as permitted sender) Received: from [209.85.216.45] (HELO mail-qa0-f45.google.com) (209.85.216.45) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Dec 2012 18:54:22 +0000 Received: by mail-qa0-f45.google.com with SMTP id j15so6940575qaq.11 for ; Sat, 22 Dec 2012 10:54:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JNpl58/v3D8H//ZGa5qauu6o/JuOyNDvPpNPosVg35I=; b=VHzHUz1tt9KISuiBSUkmxiDq3Y1SXzHlUBPY+HYwwzggLEZtGeKxQWuRy10UNdVNO8 2U5XzA6rDQgmtM9L0PJOwxvegbWYl4QtoIih5PhaVLr9V1zBaLBi90XiS4ID9ezhfIUi H/n31AEiWGsvEkVwl97A4PMjrKjc22MMTqCNbMHG4LrklIest4/WcSbZp1ymHIlgvVuW CYIvWeKfUEoWVuJ6ei76d3BHy4Lc4PEuJudDARCXiCVfBgw/dF4+Ak6FjjYGkbclNdqL O0R3DqBbhtZK/odfKg6USBRGzRbbeZIOvBq4UX78lNo/o/4PGCo497T4A6loqAIUCDcG O6kg== MIME-Version: 1.0 Received: by 10.49.73.232 with SMTP id o8mr10449064qev.0.1356202441236; Sat, 22 Dec 2012 10:54:01 -0800 (PST) Received: by 10.49.129.162 with HTTP; Sat, 22 Dec 2012 10:54:01 -0800 (PST) In-Reply-To: References: Date: Sat, 22 Dec 2012 20:54:01 +0200 Message-ID: Subject: Re: Merging files From: Barak Yaish To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7bb70dfec0e12e04d1757ce8 X-Virus-Checked: Checked by ClamAV on apache.org --047d7bb70dfec0e12e04d1757ce8 Content-Type: text/plain; charset=ISO-8859-1 Can you please attach HOW-TO links for the alternatives you mentioned? On Sat, Dec 22, 2012 at 10:46 AM, Harsh J wrote: > Yes, via the simple act of opening a target stream and writing all > source streams into it. Or to save code time, an identity job with a > single reducer (you may not get control over ordering this way). > > On Sat, Dec 22, 2012 at 12:10 PM, Mohit Anchlia > wrote: > > Is it possible to merge files from different locations from HDFS location > > into one file into HDFS location? > > > > -- > Harsh J > --047d7bb70dfec0e12e04d1757ce8 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Can you please attach HOW-TO links for the alternatives yo= u mentioned?

On Sat, Dec 22, 2012 at 10:4= 6 AM, Harsh J <harsh@cloudera.com> wrote:
Yes, via the simple act of opening a target = stream and writing all
source streams into it. Or to save code time, an identity job with a
single reducer (you may not get control over ordering this way).

On Sat, Dec 22, 2012 at 12:10 P= M, Mohit Anchlia <mohitanchlia= @gmail.com> wrote:
> Is it possible to merge files from different locations from HDFS locat= ion
> into one file into HDFS location?



--
Harsh J

--047d7bb70dfec0e12e04d1757ce8--