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 0EE258C90 for ; Thu, 1 Sep 2011 22:13:44 +0000 (UTC) Received: (qmail 10839 invoked by uid 500); 1 Sep 2011 22:13:42 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 10764 invoked by uid 500); 1 Sep 2011 22:13:41 -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 10756 invoked by uid 99); 1 Sep 2011 22:13:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 22:13:41 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of timelessness@gmail.com designates 209.85.215.41 as permitted sender) Received: from [209.85.215.41] (HELO mail-ew0-f41.google.com) (209.85.215.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2011 22:13:34 +0000 Received: by ewy9 with SMTP id 9so1691152ewy.14 for ; Thu, 01 Sep 2011 15:13:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=g04/nd6OPSTz4SerF/8zv8wgk6X9tMHuqUUw+JgV5Qo=; b=qlzll7tpAFj2MqTgLyrLHkr02lIL8l/K3xVVrVioqHxHjlhQtvYOCY5IYSWyYNYW8s 3kOM3DxkQdpahmFkdLIRfBNcJ4yDMknFLbpcG2M6Q/zGGoRO6DP7kIWINV+OjUGiCruu 7hA2x4l36FswrEQ1xKNA2zh8O84DVDYqvb8wI= MIME-Version: 1.0 Received: by 10.216.136.158 with SMTP id w30mr686620wei.40.1314915193887; Thu, 01 Sep 2011 15:13:13 -0700 (PDT) Received: by 10.216.166.76 with HTTP; Thu, 1 Sep 2011 15:13:13 -0700 (PDT) In-Reply-To: References: <11B3066F-7AB8-41ED-BBA4-EFD0F9EE5463@email.com> <1314697671.83999.YahooMailNeo@web65509.mail.ac4.yahoo.com> <20F5B80F-2DCE-425A-B3A6-66E2D47D4FF3@oracle.com> Date: Thu, 1 Sep 2011 15:13:13 -0700 Message-ID: Subject: Re: HBase and Cassandra on StackOverflow From: Time Less To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=0016e6dab5170a9ae904abe88d85 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6dab5170a9ae904abe88d85 Content-Type: text/plain; charset=ISO-8859-1 Why are you quoting "harder" what was said was "more complex". Setting up N > things is more complex then setting up a single thing. > Okay. Sorry for misinterpreting your meaning. You're right, it's more complex to set up. You are also implying that following the wiki is easy. Personally, I find > that the wiki has fine detail, but it is confusing. > True. Running a world-class distributed database isn't trivial. And yeah, sorry for implying following the wiki is easy. It was for me, but that may not be for others. > Uppercasing the word FAR does not prove to me that hbase is easier to > administer nor does the your employment history or second hand stories > unnamed from people you know. A lot of people think credentials are important, especially in this particular debate of Cassandra vs. HBase, where obviously technical details are ignored. My point is, I've worked extremely closely with the flagship deploys of both (Apache) Cassandra and HBase and continue to work closely with the people who still have to run this stuff at volume today. I'm sorry you don't find these details important. [2] I went from having never set up HBase nor ever used Chef to having > functional Chef recipes that installed a functional HBase/HDFS cluster in > about 2 weeks. > > It took me about one hour to accomplish the same result with puppet + > cassandra. > http://www.jointhegrid.com/highperfcassandra/?p=62 > Something being easy to set up is entirely different than it working at scale. Note I don't mention how long it took me to set up SQL Lite or write Chef recipes for it. The whole point of Puppet and Chef is to manage complexity, which you'll need when running a world-class distributed database. -- Tim Ellis Data Architect, Riot Games --0016e6dab5170a9ae904abe88d85--