Return-Path: X-Original-To: apmail-hadoop-general-archive@minotaur.apache.org Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1E43EE724 for ; Wed, 9 Jan 2013 07:28:29 +0000 (UTC) Received: (qmail 56314 invoked by uid 500); 9 Jan 2013 07:28:27 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 56011 invoked by uid 500); 9 Jan 2013 07:28:26 -0000 Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@hadoop.apache.org Delivered-To: mailing list general@hadoop.apache.org Received: (qmail 55987 invoked by uid 99); 9 Jan 2013 07:28:26 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 07:28:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.220.180] (HELO mail-vc0-f180.google.com) (209.85.220.180) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 07:28:18 +0000 Received: by mail-vc0-f180.google.com with SMTP id p16so1246199vcq.39 for ; Tue, 08 Jan 2013 23:27:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=rm4JNZvJotG48NZHxSv9PjmriuY16jiiZz5pvOzt14g=; b=gitLaKzFftJQ/T/qh4quRbb7DZfs1pkBgkutHEhFS9jdqqxmgeMsLEy5r8nWmPl0u0 gC/Opqf2elXSabY0zdTlXHphJ6KMpKBKuQ6ZfgZEhDOywSKr74fq5JWRyAmqXzMhNlbQ HVgo3T0wdu1xiq4N3YZKbKfI5ct4f2k3dVMltBEkMtu50gExP/kdcLBeueXHPXqvZaaZ jSj4cIG2fVDKKCL1wF8kxBeHu3Le4VuGlKLj2ddgwS027tQcttM03IA+VADUoD1mkutA Pzct6N4FVV0MtmjX63+bdUYF1noo9s9nKHZJBYvyzxNSEorfd+IALc1TQ3Hm16/WH5zh wFgA== Received: by 10.52.97.7 with SMTP id dw7mr77571270vdb.38.1357716477021; Tue, 08 Jan 2013 23:27:57 -0800 (PST) MIME-Version: 1.0 Received: by 10.58.164.133 with HTTP; Tue, 8 Jan 2013 23:27:36 -0800 (PST) In-Reply-To: References: From: Ted Dunning Date: Tue, 8 Jan 2013 23:27:36 -0800 Message-ID: Subject: Re: Question about protocol buffer RPC To: general@hadoop.apache.org Content-Type: multipart/alternative; boundary=20cf307f31a4518e9804d2d60095 X-Gm-Message-State: ALoCoQlkE9lPk6/61WDDWAM8Zh8adr7LMdsIu0/aGzNXSj2Rgg884awTTFsM1PIg1Rg6HZkq0Cl1 X-Virus-Checked: Checked by ClamAV on apache.org --20cf307f31a4518e9804d2d60095 Content-Type: text/plain; charset=ISO-8859-1 Avro and Thrift both work well for RPC implementations. I have lately been using protobufs with protobuf-rpc-pro and have been very happy with it. It has much of the debuggability of Thrift, but with protobufs. See http://code.google.com/p/protobuf-rpc-pro/ On Tue, Jan 8, 2013 at 8:44 PM, Hangjun Ye wrote: > Our project is facing similar problem: choosing a PRC framework. > So I want to know if there are any drawbacks in Avro/Thrift and then Hadoop > doesn't use them. > > Would appreciate if any insights could be shared for this! > > > 2013/1/9 Hangjun Ye > > > Hi there, > > > > Looks Hadoop is using Google's protocol buffer for its RPC (correct me if > > I'm wrong). > > > > Avro/Thrift do the same thing, support more language, and have a complete > > PRC implementation. Seems Google's protocol buffer PRC only has a > framework > > but doesn't include implementation with a concrete network framework. > > > > So just curious the rationale behind this? > > > > -- > > Hangjun Ye > > > > > > -- > Hangjun Ye > --20cf307f31a4518e9804d2d60095--