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 1D1F410EBC for ; Thu, 8 Aug 2013 00:59:08 +0000 (UTC) Received: (qmail 89890 invoked by uid 500); 8 Aug 2013 00:59:06 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 89829 invoked by uid 500); 8 Aug 2013 00:59:06 -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 89821 invoked by uid 99); 8 Aug 2013 00:59:06 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Aug 2013 00:59:06 +0000 X-ASF-Spam-Status: No, hits=2.8 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,URI_HEX X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kelvin.msj@gmail.com designates 209.85.212.180 as permitted sender) Received: from [209.85.212.180] (HELO mail-wi0-f180.google.com) (209.85.212.180) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Aug 2013 00:59:00 +0000 Received: by mail-wi0-f180.google.com with SMTP id f14so33762wiw.1 for ; Wed, 07 Aug 2013 17:58:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Meqvz7eHDMhZipnMx5FBnMUSF2ndsSrSmAyAenERt7I=; b=lKNHCXHWLKXda0UzXiXlRZqG3z8a/9fRN8xHsx08WBXu0LRgUtfoSo7haVte5i9Uaa M/H1gH5jBd32TbZiZvDwkJ8GUF1IutgxrvPk20XyA0sM757CjNmJboMADqG4qxUXkd+k 4VrLNZQ+DOrBquF7D1JiFxhgiAXC1vh+rAyT5sMOf6K9GLGKFWn8uXy0EQb85Uu7oC5t 8rDaTX6/8uqlXc7DJix77mDi0xFl/dtyk/H3RGFQiCyMgIbGMUaeM7FtFRtCu3u38F6u Hyn9jV8keypOgkF//zWXTVg5GgtMwcuj0NGko9k1X8HVCXS1oQp+T3GSCpdFKbVgml+j fERA== MIME-Version: 1.0 X-Received: by 10.194.172.9 with SMTP id ay9mr1969457wjc.54.1375923520068; Wed, 07 Aug 2013 17:58:40 -0700 (PDT) Received: by 10.216.219.132 with HTTP; Wed, 7 Aug 2013 17:58:40 -0700 (PDT) In-Reply-To: <1375873107580-4048942.post@n3.nabble.com> References: <1375873107580-4048942.post@n3.nabble.com> Date: Thu, 8 Aug 2013 08:58:40 +0800 Message-ID: Subject: Re: Loading Data Into HBase From: Shengjie Min To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=089e01184dd6a6e31504e3652860 X-Virus-Checked: Checked by ClamAV on apache.org --089e01184dd6a6e31504e3652860 Content-Type: text/plain; charset=ISO-8859-1 1stly, why you wanna move away from MongoDB to HBase? well, if it's a RDBMS we are talking about here, sqoop sounds like the tool you should be using. But seems it's mongoDB, you will have to look into Flume/Scribe and see if it's feasible. Shengjie On 7 August 2013 18:58, JC wrote: > I have just started on a real/near time data loading project working with > HBase as the data store. The primary, but not only, source of the data that > I need to load is stored in mongodb. I do expect volumes to be high, > although with the near to real time loads this may be minimized. I am > relatively new to HBase and wanted draw on the knowledge and experiences > from this group. I was hoping to get some ideas on best practices or > solutions that have been used in this type of scenario for loading data > into > HBase? Also, has anyone used any tools to make this easier instead of hand > coding it all? > > Thanks in advance, > JC > > > > -- > View this message in context: > http://apache-hbase.679495.n3.nabble.com/Loading-Data-Into-HBase-tp4048942.html > Sent from the HBase User mailing list archive at Nabble.com. > -- All the best, Shengjie Min --089e01184dd6a6e31504e3652860--