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 09662DD44 for ; Wed, 31 Oct 2012 05:14:30 +0000 (UTC) Received: (qmail 12901 invoked by uid 500); 31 Oct 2012 05:14:25 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 12698 invoked by uid 500); 31 Oct 2012 05:14:25 -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 12669 invoked by uid 99); 31 Oct 2012 05:14:24 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 05:14:24 +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.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Oct 2012 05:14:17 +0000 Received: by mail-ie0-f176.google.com with SMTP id k11so1777690iea.35 for ; Tue, 30 Oct 2012 22:13:56 -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=eC27CO3fG4DTBGs8MAKyAzEMea3B7D4KK4B9li/S034=; b=kqeQjIBSLOPMlSZPtbf+1XfK9vJ8/hdB7fRU8XwQHapn2kI7KJ1JlAB7J/1ylUkH/9 MioH0CBOFrsAqORpcvaWhUX6kKL4TAuQl5w0o34CN2JRhBpGj4mYZu7io+XsnqdtqzgM R87WPJ6fV3Rgc/YN3jXUKKv0keyXJlS02czNd5kdid2Et7bUpmxrYAh5fZqqPuvVmSxC kz8693ZVNm2vzF6fAgg8+6/LWBYZxFpSCVQNS0DsA38Dp4/edz07k5L2b/wM6jHfKxxT Zoys2kXplLLsQdQh2YCb6ch6AvGKoAePpBZN89JQ607o4MFy/JPhGYgkU3vbGvAxya9v W+CQ== Received: by 10.50.183.167 with SMTP id en7mr328754igc.49.1351660436313; Tue, 30 Oct 2012 22:13:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.27.8 with HTTP; Tue, 30 Oct 2012 22:13:36 -0700 (PDT) In-Reply-To: <1F68EA0E0CBFBE44A9A64274E1AC01A11D00C1B1A6@DFW1MBX23.mex07a.mlsrvr.com> References: <1351659118.62482.ezmlm@hadoop.apache.org> <1F68EA0E0CBFBE44A9A64274E1AC01A11D00C1B1A6@DFW1MBX23.mex07a.mlsrvr.com> From: Harsh J Date: Wed, 31 Oct 2012 10:43:36 +0530 Message-ID: Subject: Re: updates in hdfs To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkCaCGxLkcykeJIne4dJ6JyFx4bgAvF6MlyHDkJ5XmwTz8bZY4pqRpvV3OACxXA+b83yLli X-Virus-Checked: Checked by ClamAV on apache.org Shiv, HDFS does have file-append support (i.e. add data at end of a previously closed file). HDFS does not have random-write support (i.e. writing data at a selected offset in the file). What is your use-case though, that you seek to do updates over files on HDFS? Perhaps you are instead looking for HBase, which has a slightly different way of storing things but provides updates+versions in a way over HDFS. On Wed, Oct 31, 2012 at 10:28 AM, Siva Gudavalli wrote: > Hi, > > Is there any mechanism on how to do updates to a files on hdfs? > > Regards > shiv -- Harsh J