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 DA4FD99A0 for ; Sun, 25 Mar 2012 13:05:59 +0000 (UTC) Received: (qmail 84350 invoked by uid 500); 25 Mar 2012 13:05:58 -0000 Delivered-To: apmail-hbase-user-archive@hbase.apache.org Received: (qmail 84194 invoked by uid 500); 25 Mar 2012 13:05:58 -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 84184 invoked by uid 99); 25 Mar 2012 13:05:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2012 13:05:58 +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 (athena.apache.org: domain of rmorgan466@gmail.com designates 209.85.216.48 as permitted sender) Received: from [209.85.216.48] (HELO mail-qa0-f48.google.com) (209.85.216.48) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 25 Mar 2012 13:05:51 +0000 Received: by qam2 with SMTP id 2so1926805qam.14 for ; Sun, 25 Mar 2012 06:05:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=f+9xSUIMrzpoOMu6bGnC2NW2CY2atKdGctC7eZQVNI0=; b=dNdLccvnAPgyi/1asUc3tymsrs5r+SHUIQENaq3O7cd8l2dE8GqjdHyAr7q0TE1Pk1 dGwfBWmlxB52bhYuGUmNK0JILEv4CWgMkb+TjSE61a6o3WFSUyxBOpfk/zuz/KTyR7sl 525QRApSWelge0h+BuFp17mlEJAWT+iEaTfsm1aLBAdc9TyxJJFH7/OGq6MbrhZTPN05 ffc8toaXJwmLhku/EIw9tXP2lm9BTcq68F+UjGBkrqIiLj6RS+bHIpdipRtpS36LPUqP 97asUxH9O2QniUkHraxfFjY5DRTReqObZp7SPYFny9IIN9DW/stlet5SgRAQYuJwUOHx 2kCg== MIME-Version: 1.0 Received: by 10.224.184.70 with SMTP id cj6mr23562369qab.77.1332680731172; Sun, 25 Mar 2012 06:05:31 -0700 (PDT) Received: by 10.229.226.68 with HTTP; Sun, 25 Mar 2012 06:05:31 -0700 (PDT) Date: Sun, 25 Mar 2012 09:05:31 -0400 Message-ID: Subject: thrift or avro From: Rita To: user@hbase.apache.org Content-Type: multipart/alternative; boundary=20cf303b421994a0c204bc10e928 X-Virus-Checked: Checked by ClamAV on apache.org --20cf303b421994a0c204bc10e928 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Currently, I am connecting to Hbase, Trift and Python and was curious if 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. --=20 --- Get your facts first, then you can distort them as you please.-- --20cf303b421994a0c204bc10e928--