Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Received-SPF: pass (athena.apache.org: local policy)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; CHARSET=US-ASCII; delsp=yes; format=flowed
Date: Mon, 29 Jun 2009 08:09:57 -0700
From: George Porter <George.Porter@Sun.COM>
Subject: Re: who's doing what for 0.21?
In-reply-to: <78568af10906240035v4b9c6d7dwad5e75ec441b620f@mail.gmail.com>
Sender: George.Porter@Sun.COM
To: avro-dev@hadoop.apache.org
Cc: hbase-dev@hadoop.apache.org
Message-id: <58C11BA6-8F5F-4921-9673-9F7B31684BD4@Sun.com>
References: <475316.13696.qm@web65509.mail.ac4.yahoo.com>
 <E9C6F5B134FDA3468879CB4E533CF1C803709D@TK5EX14MBXC111.redmond.corp.microsoft.com>
 <227781.87293.qm@web65515.mail.ac4.yahoo.com> <4A4057E2.3000708@cloudera.com>
 <78568af10906222136mf9da956xcdb19b617cb9bd96@mail.gmail.com>
 <c9118d4c0906232355g310d1567wf06b6c1e1f3623f@mail.gmail.com>
 <78568af10906240035v4b9c6d7dwad5e75ec441b620f@mail.gmail.com>

I'd be happy to look into bottom up profiling with tracer tags (path- 
based metadata field) supported with avro.  I implemented similar  
tracing with Thrift by including an optional parameter into each RPC  
by default which passed along metadata.  If the receiver didn't  
understand it, it would just ignore that parameter, and if the client  
didn't support it, then the receiver would just use a default value of  
null.  It seems like a similar approach could be taken with Avro, and  
I'll check that out this week.

Thanks,
George

On Jun 24, 2009, at 12:35 AM, Ryan Rawson wrote:

> Here are some thoughts:
>
> - Performance is important.
> - Unified protocol would help the use of tracer tags, which could give
> us top to bottom profiling.
> - Would like to do rolling restart of HBase, even under relatively
> major upgrades.
> - PHP (even pure php) bindings.
>
> I'll poke at the code, what is the current state?
>