Return-Path: X-Original-To: apmail-hbase-user-archive@www.apache.org Delivered-To: apmail-hbase-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 527AC10A16 for ; Mon, 6 May 2013 17:34:24 +0000 (UTC) Received: (qmail 25052 invoked by uid 500); 6 May 2013 17:34:22 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 24997 invoked by uid 500); 6 May 2013 17:34:22 -0000 Mailing-List: contact user-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hbase.apache.org Delivered-To: mailing list user@hbase.apache.org Received: (qmail 24989 invoked by uid 99); 6 May 2013 17:34:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 May 2013 17:34:22 +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 jdcryans@gmail.com designates 209.85.128.170 as permitted sender) Received: from [209.85.128.170] (HELO mail-ve0-f170.google.com) (209.85.128.170) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 May 2013 17:34:16 +0000 Received: by mail-ve0-f170.google.com with SMTP id 15so3481448vea.15 for ; Mon, 06 May 2013 10:33:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=IDghALt3CuuHJDRug2pqwT5AvCUXtgHX4UWPBuzGkpM=; b=uiBiqtZKcXMbwJ7e/NVOq2p2PcjduscV7WFyqLgADOmn7+XSXnPOQQhdbKOfrabJIm 65ZsfMz0ulfF1T2q6NoNSYts/mmfSTXjmpZS5qBHVJ0ULE7CknTlUs0wifib34viBBU3 0bsmdVbsWAgwrZszrjQR7qNChL/sX1BzeoNyxEvGb2zQfJrv3jm7LsqfPcb3mqF/kYAw pXIHO6L5yVoGLfPtUc8DqPKwNdsP9idrjcNv44yAjYJcyB96dIE3h0Yl/cZsaChztaJb mDbilu1lF3U2HnSOYHZJaKF+c1oLTFh6b8XETE7Dzl0XCJmuI7g/Q7OVhWTouYxRUHY+ 8OsA== MIME-Version: 1.0 X-Received: by 10.52.176.163 with SMTP id cj3mr6059646vdc.35.1367861635928; Mon, 06 May 2013 10:33:55 -0700 (PDT) Sender: jdcryans@gmail.com Received: by 10.220.113.206 with HTTP; Mon, 6 May 2013 10:33:55 -0700 (PDT) In-Reply-To: References: Date: Mon, 6 May 2013 10:33:55 -0700 X-Google-Sender-Auth: Sv9AMsR341mFjijwa0KTvHYQUas Message-ID: Subject: Re: Extract a whole table for a given time(stamp) From: Jean-Daniel Cryans To: "user@hbase.apache.org" Content-Type: multipart/alternative; boundary=bcaec5015d0fe95c7904dc101a53 X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5015d0fe95c7904dc101a53 Content-Type: text/plain; charset=ISO-8859-1 You can use the Export MR job provided with HBase, it lets you set a time range: http://hbase.apache.org/book.html#export J-D On Mon, May 6, 2013 at 10:27 AM, Gaurav Pandit wrote: > Hi Hbase users, > > We have a use case where we need to know how data looked at a given time in > past. > > The data is stored in HBase of course, with multiple versions. And, the > goal is to be able to extractall records (rowkey, columns) as of a given > timestamp, to a file. > > > I am trying to figure out the best way to achieve this. > > The options I know are: > 1. Write a *Java* client using HBase Java API, and scan the hbase table. > 2. Do the same, but over *Thrift* HBase API using Perl (since > our environment is mostly Perl). > 3. Use *Hive *to point to HBase table, and use Sqoop to extract data from > the Hive table and onto client / RDBMS. > 4. Use *Pig *to extract data from HBase table and dump it on HDFS and move > the file over to the client. > > So far, I have successfully implemented option (2). I am still running some > tests to see how it performs, but it works fine as such. > > My questions are: > 1. Is option (3) or (4) even possible? I am not sure if we can access the > table for a given timestamp over Pig or Hive. > 2. Is there any other better way of achieving this? > > > Thanks! > Gaurav > --bcaec5015d0fe95c7904dc101a53--