Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 471281080F for ; Sat, 3 Jan 2015 16:17:25 +0000 (UTC) Received: (qmail 3617 invoked by uid 500); 3 Jan 2015 16:17:19 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 3518 invoked by uid 500); 3 Jan 2015 16:17:19 -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 3484 invoked by uid 99); 3 Jan 2015 16:17:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jan 2015 16:17:06 +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 wilm.schumacher@gmail.com designates 209.85.212.175 as permitted sender) Received: from [209.85.212.175] (HELO mail-wi0-f175.google.com) (209.85.212.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Jan 2015 16:16:59 +0000 Received: by mail-wi0-f175.google.com with SMTP id l15so978429wiw.2 for ; Sat, 03 Jan 2015 08:15:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=ua+KRS/koBY8GK09qiN9LLv+tKv5X1OjpAW7X6ObyKY=; b=xZuXHImjBUdlRDBEtEyYTflieO0lAmGv0M/JQvDcjB+8craNwOwE6/LN/J2V4cq46T FlnhppjcB+nwh12lG9g9QItydGLojangrdJO5XjQIJb13dEOhqLDnAzHQuOkj4fy3AMY 6PD2oWM9ChEfQgvRHSHnEr5RZVysUACNxmVKDkfSAE6G8oJKgtrRTqbNir/BJ3VB/NdT 5q3DDh6fbu0Z2tCNGLbnjlXKqkhy9Q2CzeR/YPB+nAx2qSn+shk/WVW6flBPRzI5u4W7 B+gg/kyOuondVyGcRGGYBvGb5NHnWee30wnawrFy9cP3RYOwEM7AaUdw5J5i6lmhThrg 8l/g== X-Received: by 10.194.52.37 with SMTP id q5mr157740142wjo.39.1420301753786; Sat, 03 Jan 2015 08:15:53 -0800 (PST) Received: from [192.168.1.2] (i5E86DB2D.versanet.de. [94.134.219.45]) by mx.google.com with ESMTPSA id u3sm2986468wiw.24.2015.01.03.08.15.52 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 03 Jan 2015 08:15:53 -0800 (PST) Message-ID: <54A815BD.1000005@gmail.com> Date: Sat, 03 Jan 2015 17:15:57 +0100 From: Wilm Schumacher User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: user@hadoop.apache.org Subject: Re: HDFS-based database for Big and Small data? References: <54A80D17.8010806@gmail.com> <88900BD3-D709-4AC3-B14D-DF42EB4D63B4@gmail.com> In-Reply-To: <88900BD3-D709-4AC3-B14D-DF42EB4D63B4@gmail.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Am 03.01.2015 um 16:50 schrieb Jay Vyas: > 1) Phoenix can be used on top of hbase for richer querying semantics. That combo might be good for complex workloads. > > 2) SolrCloud also might fit the bill here ? > > Solr can be backed by any HAdoop compatible FS including HDFS, and it's resiliant by that mechanism, and offers sophisticated indexing and searching options. > > Although the querying is limited... I agree of course. But perhaps the additional layer of complexity isn't necessary. Depends on the requirements. Best wishes, Wilm