Return-Path: 
 <user-return-12981-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-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 59F4110694
	for <apmail-hadoop-mapreduce-user-archive@minotaur.apache.org>;
 Sat,  4 Jan 2014 10:30:29 +0000 (UTC)
Received: (qmail 43909 invoked by uid 500); 4 Jan 2014 10:30:16 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 43418 invoked by uid 500); 4 Jan 2014 10:30:03 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 43222 invoked by uid 99); 4 Jan 2014 10:30:00 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jan 2014 10:30:00 +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 vjshalish@gmail.com
 designates 209.85.212.171 as permitted sender)
Received: from [209.85.212.171] (HELO mail-wi0-f171.google.com)
 (209.85.212.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Jan 2014 10:29:54 +0000
Received: by mail-wi0-f171.google.com with SMTP id bz8so1259281wib.4
        for <user@hadoop.apache.org>; Sat, 04 Jan 2014 02:29:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=nrwtxiRQ1YKQhe+fcF/po8nI7hgPmsTf5g/6t3Nsz/A=;
        b=Bb9TDbeq+Dw2ayIa0eU1uBWvw79TRr2u/ICSBull7bp4abl0kAwGaDnj2DoDuLg9Mv
         aME4ewbdVZyOdqtq/CmTrlwTyr/HlMFidmUSu1pyz2Jp5hxy/6Ii9akTKddBir5DW1uU
         Dp3uS4t4q8K3EiWifSoknaFZ9qZxUDPnHLgaiz3u6u06uK+uu8ecBklex3CCFLwvm57s
         mXlda0s+AplYzMU8/jcU0Vmrv3DTAQH5jh9FaBUWKgRC4SlIFYqyrzkgHUJh95+NriG+
         10/IFHDTtkkHGkQDcoYbPaa48tUviolfiqh7w9R09DcVO/Oh+tSDzAKrSp5xA7B20bGV
         w/zw==
MIME-Version: 1.0
X-Received: by 10.194.241.228 with SMTP id wl4mr64906892wjc.2.1388831373650;
 Sat, 04 Jan 2014 02:29:33 -0800 (PST)
Received: by 10.216.53.206 with HTTP; Sat, 4 Jan 2014 02:29:33 -0800 (PST)
Date: Sat, 4 Jan 2014 15:59:33 +0530
Message-ID: 
 <CAGo9O0b0a=Rqm=0bJsQ2zcf3p29r87g+2X0gZEHAtFvyX-1Wcw@mail.gmail.com>
Subject: Cutting a line in between while creating blocks
From: VJ Shalish <vjshalish@gmail.com>
To: Hadoop User Mailer List <user@hadoop.apache.org>
Content-Type: multipart/alternative; boundary=089e01493c32adef8b04ef228096
X-Virus-Checked: Checked by ClamAV on apache.org

--089e01493c32adef8b04ef228096
Content-Type: text/plain; charset=ISO-8859-1

Hi,

While creating the blocks for a file containing n number of lines, how does
Hadoop take care of the problem of not Cutting a line in  between while
creating blocks?
Is it taken care of by Hadoop?

Thanks
Shalish.

--089e01493c32adef8b04ef228096
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi,</div><div>=A0</div><div>While creating the blocks=
 for a file containing n number of lines, how does Hadoop take care of the =
problem of not Cutting a line in=A0 between while creating blocks?</div><di=
v>Is it taken care of by Hadoop?</div>
<div>=A0</div><div>Thanks</div><div>Shalish.</div></div>

--089e01493c32adef8b04ef228096--