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 18B02D307 for ; Wed, 7 Nov 2012 15:05:26 +0000 (UTC) Received: (qmail 63243 invoked by uid 500); 7 Nov 2012 15:05:21 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 63063 invoked by uid 500); 7 Nov 2012 15:05:20 -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 63051 invoked by uid 99); 7 Nov 2012 15:05:20 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Nov 2012 15:05:20 +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 (nike.apache.org: domain of harsh@cloudera.com designates 209.85.210.176 as permitted sender) Received: from [209.85.210.176] (HELO mail-ia0-f176.google.com) (209.85.210.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 07 Nov 2012 15:05:12 +0000 Received: by mail-ia0-f176.google.com with SMTP id h11so1310032iae.35 for ; Wed, 07 Nov 2012 07:04:52 -0800 (PST) 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=nRA6Kq/Ol33fOc3FBYxH0R6mlHlhRp3pjCptUxlmp0c=; b=eJnRoeh/+pKoYx4uu61hzzGDegjtmA82Jear+5iOMk7iPlmEQNy58qU2xWK542By5B X1OSRSmHDlOXYdO+6+7p9A082nbunY+ibYUZ1qkXqPn9ye3co/kCXvte2p5jmx8rxMgp yu3+LoBtgUH0g9FKudycEMnEMLvLr8jgzpkLPVYSYhTSlJAPvZo+UBUOtL06JCT7fuYE IBEcCE5hwhKim+bIc8P0zDrObMM15ZvQGGt9uLtDHQ9dWGx9sQs02s0CAe4ra35yhsc4 8V9WjKCx/9x+vGk8Re1KMKMg/rkePgWotxiSXHVQzJiPZRWmhf5NVWhdjnBm3Lf01wlM fMTQ== Received: by 10.50.183.167 with SMTP id en7mr4800071igc.49.1352300692033; Wed, 07 Nov 2012 07:04:52 -0800 (PST) MIME-Version: 1.0 Received: by 10.64.27.8 with HTTP; Wed, 7 Nov 2012 07:04:22 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Wed, 7 Nov 2012 20:34:22 +0530 Message-ID: Subject: Re: Regarding loading Image file into HDFS To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQl1NvbbSyQvs8M93ZvNP0P9yRYtkxu+iQDyeERX2b1nPsWs8/+wCNt8PgiMNTGu06dvYcBX X-Virus-Checked: Checked by ClamAV on apache.org Hi, Blocks are split at arbitrary block size boundaries. Readers can read the whole file by reading all blocks together (this is transparently handled by the underlying DFS reader classes itself, a developer does not have to care about it). HDFS does not care about what _type_ of file you store, its agnostic and just splits it based on the block size. Its up to the apps to not split a reader across blocks if it can't be parallelized. On Wed, Nov 7, 2012 at 8:22 PM, Ramasubramanian Narayanan wrote: > Hi, > > I have basic doubt... How Hadoop splits an Image file into blocks and puts > in HDFS? Usually Image file cannot be splitted right how it is happening in > Hadoop? > > regards, > Rams -- Harsh J