Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 64D46C1CB for ; Sun, 16 Jun 2013 15:07:33 +0000 (UTC) Received: (qmail 64365 invoked by uid 500); 16 Jun 2013 15:07:28 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 63904 invoked by uid 500); 16 Jun 2013 15:07: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 63897 invoked by uid 99); 16 Jun 2013 15:07:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jun 2013 15:07:27 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of harsh@cloudera.com designates 209.85.160.42 as permitted sender) Received: from [209.85.160.42] (HELO mail-pb0-f42.google.com) (209.85.160.42) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 16 Jun 2013 15:07:23 +0000 Received: by mail-pb0-f42.google.com with SMTP id un1so1977650pbc.29 for ; Sun, 16 Jun 2013 08:07:03 -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:x-gm-message-state; bh=YSvFUYiDWG/7dH4ETrq9BDCNO8u7NwcTKZsJiC4/ssQ=; b=YgRN9o8/F+fBkyEZEgEWfgnO5I8VmwGzMWXk2I1RHhEBNgT7fPYcKQlSY+HUdmRz4D VeI6DYP085cMzzhzytTY3wmfTkGIbeiurB4rLnaJQ9uxS68yPrWJgq/mMDhgWfefK+q2 33Ce/BSV2sE+zwAUPnhNbfnIvy01zfPevZcnhgMTvUmajF8gBzSyDJeoE6n6e9RyHQOV dgz93TZe1vgV/MM7BUs8eJtvVv80+0XNc5eALGK/VSQKrCEmo/qXDNgT2Tr2beSfJyzs oRc6onssf++pWxem4OFRkTuonwwAHblHu+ztFLp1CEjH/IoBrlPoRT2WWA7nt8RJc1DL f0XQ== X-Received: by 10.68.226.99 with SMTP id rr3mr9854909pbc.35.1371395223077; Sun, 16 Jun 2013 08:07:03 -0700 (PDT) MIME-Version: 1.0 Received: by 10.70.75.168 with HTTP; Sun, 16 Jun 2013 08:06:43 -0700 (PDT) In-Reply-To: <869970D71E26D7498BDAC4E1CA92226B658C6C83@MBX021-E3-NJ-2.exch021.domain.local> References: <869970D71E26D7498BDAC4E1CA92226B658C6C83@MBX021-E3-NJ-2.exch021.domain.local> From: Harsh J Date: Sun, 16 Jun 2013 20:36:43 +0530 Message-ID: Subject: Re: HDFS file reader and buffering To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQlGoKSueCn+Mr23RPXCMccQhNJv4CWtoeU5JdAPUThQfpLN3sFRKUOce8wpu72kQ330odtc X-Virus-Checked: Checked by ClamAV on apache.org Yes they do maintain a buffer equal to the configurable size of io.file.buffer.size (4k default) for both reads and writes. On Sun, Jun 16, 2013 at 7:03 PM, John Lilley wrote: > Do the HDFS file-reader classes perform internal buffering? > > Thanks > > John > > > > -- Harsh J