Return-Path: Delivered-To: apmail-hadoop-general-archive@minotaur.apache.org Received: (qmail 19954 invoked from network); 6 Apr 2009 21:03:00 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Apr 2009 21:03:00 -0000 Received: (qmail 89413 invoked by uid 500); 6 Apr 2009 21:02:59 -0000 Delivered-To: apmail-hadoop-general-archive@hadoop.apache.org Received: (qmail 89325 invoked by uid 500); 6 Apr 2009 21:02:59 -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 89315 invoked by uid 99); 6 Apr 2009 21:02:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 21:02:59 +0000 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.18.43.132] (HELO sca-es-mail-1.sun.com) (192.18.43.132) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Apr 2009 21:02:50 +0000 Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n36L2Uek015980 for ; Mon, 6 Apr 2009 14:02:30 -0700 (PDT) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; delsp=yes; format=flowed; charset=US-ASCII Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) id <0KHP008005U8ON00@fe-sfbay-09.sun.com> for general@hadoop.apache.org; Mon, 06 Apr 2009 14:02:30 -0700 (PDT) Received: from [192.168.1.40] ([unknown] [129.150.20.106]) by fe-sfbay-09.sun.com (Sun Java(tm) System Messaging Server 7.0-5.01 64bit (built Feb 19 2009)) with ESMTPSA id <0KHP005T36G4W8A0@fe-sfbay-09.sun.com> for general@hadoop.apache.org; Mon, 06 Apr 2009 14:02:29 -0700 (PDT) Date: Mon, 06 Apr 2009 14:02:28 -0700 From: George Porter Subject: Re: [PROPOSAL] new subproject: Avro In-reply-to: <49DA6AA6.8010307@apache.org> Sender: George.Porter@Sun.COM To: general@hadoop.apache.org Message-id: <51A0963D-4522-4D16-95AF-125AFEC150E2@Sun.com> X-Mailer: Apple Mail (2.930.3) References: <417838.23294.qm@web65509.mail.ac4.yahoo.com> <49DA6154.3040006@apache.org> <1D314A78-E219-41DC-9900-CABEEE26AC55@Sun.com> <49DA6AA6.8010307@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org > > Unfortunately, that patch stalled awaiting benchmarks, and now is > stale. Avro currently specifies a request and response payload > format, but does not say much about metadata. In an HTTP-based > transport, tracing might be done through headers. As we adapt > Hadoop's optimized RPC transport to support Avro messages we should > probably insert a generic metadata layer, analogous to HTTP's > headers, to support features such as this. > > Doug Doug, This would be great. While it is always possible to add extension data to the payload itself, having such support in the transport itself can be quite useful, in my opinion. Especially if there are a variety of different payloads, you don't have to extend each one. -George