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 9EE549572 for ; Mon, 26 Mar 2012 23:54:20 +0000 (UTC) Received: (qmail 91814 invoked by uid 500); 26 Mar 2012 23:54:19 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 91763 invoked by uid 500); 26 Mar 2012 23:54:19 -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 91753 invoked by uid 99); 26 Mar 2012 23:54:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 23:54:18 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of rmorgan466@gmail.com designates 209.85.216.41 as permitted sender) Received: from [209.85.216.41] (HELO mail-qa0-f41.google.com) (209.85.216.41) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 26 Mar 2012 23:54:12 +0000 Received: by qafl39 with SMTP id l39so2870192qaf.14 for ; Mon, 26 Mar 2012 16:53:51 -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=tCz88M/C6DAhddFc9kcnhXyTWhakht/WvhQXATG4QnY=; b=eBzmnheyV/+7Le9uqPErYLEDJedzTHwOvzdBh4GqZHf1YcBqO597ctan1dnhftt7jV TZpsKE7FHahsljqpb5izny4y0+LagmQhi8GY2aOVYTuVuj/QzAYeGj55F9xacNHhR014 klyREIHYs66BPZgbxbsIE/j3r+i5/niqJhHr2qUNJF8XA6/CCfsV96ZIVt8gsLaqt63h LKc/k27ndzl9uDpAQGDtl3iymyOJOvwNZrSP268s2EyFOYZ3DozHSZDd3lQHong6BUUH d5TSk/8g+GnmxowWtWa4+pmV9c7NLtEyjXnW/Vl+ZmF4aNi8Z+xy27gbXWRdwltBsFBv z2nA== MIME-Version: 1.0 Received: by 10.229.106.193 with SMTP id y1mr9429994qco.73.1332806031422; Mon, 26 Mar 2012 16:53:51 -0700 (PDT) Received: by 10.229.226.68 with HTTP; Mon, 26 Mar 2012 16:53:51 -0700 (PDT) In-Reply-To: References: Date: Mon, 26 Mar 2012 19:53:51 -0400 Message-ID: Subject: Re: thrift or avro From: Rita To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=0023544706b00eb4e204bc2e16ed --0023544706b00eb4e204bc2e16ed Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Thanks. You answered my question. 0.94 looks really exciting! On Mon, Mar 26, 2012 at 11:19 AM, Stack wrote: > On Sun, Mar 25, 2012 at 6:05 AM, Rita wrote: > > Currently, I am connecting to Hbase, Trift and Python and was curious i= f > > Avro does something similar to Thrift. The problem with thrift is it > > doesn=B4t support coprocessors and other features of hbase. Would Avro = do a > > better job of handling? Also, what is a typical use case of Avro and > Hbase > > -- I see people at Wibi data use it and was very intrigued. > > > > The thrift gateway is getting dev love; see 0.94 or TRUNK. The avro > gateway has seen little change since it was originally added. > > What are you missing from thrift? > > The lads and lasses over at wibidata use avro in a different > dimension, in a layer they have built above hbase into which they have > built some interesting facility. I doubt they use the hbase avro > gateway at all. > > St.Ack > --=20 --- Get your facts first, then you can distort them as you please.-- --0023544706b00eb4e204bc2e16ed--