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)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Message-ID;
  b=k/rGJtdTG9pVplBBtuWGO+M0bSt0eOmocDy/NaSLM43M2v0IODm51JAUbbb8ZMEJlwfMP1TbevrRsLB+7fpLiX75j0g0SCTWTnIXJNgKIwyftPyf1gR2Jvn0Ry/SrnnR4Pc9wmhagpI3j0OJIbFIVlV0CrtxOd4u3GhfnBM/F/Y=;
Date: Wed, 19 Nov 2008 13:04:54 -0800 (PST)
From: Andrew Purtell <apurtell@yahoo.com>
Reply-To: apurtell@apache.org
Subject: Re: JSON support for HBaseRest
To: Brian Beggs <bbeggs@enernoc.com>
Cc: hbase-dev@hadoop.apache.org
In-Reply-To: 
 <A9052DE662DF3C478FA77DE37730152002507224@enbossrv03.EnerNOC.local>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Message-ID: <314172.17447.qm@web65502.mail.ac4.yahoo.com>

Brian,

Please see: 

    https://issues.apache.org/jira/browse/HBASE-814

    https://issues.apache.org/jira/browse/HBASE-815

for earlier work. However Michael has not completed work on
these issues and is not an active participant right now. If
you would like to pick up this work and/or reimplement it or
something similar for HBase trunk, this would be most
appreciated and well received.

   - Andy

> From: Brian Beggs <bbeggs@enernoc.com>
> Subject: JSON support for HBaseRest
> To: hbase-dev@hadoop.apache.org
> Date: Wednesday, November 19, 2008, 12:43 PM
>
> I am currently working on adding JSON support to the HBase
> Rest implementation.  I wanted to contact the HBase developer
> community to see if either something like this was already
> being worked on and if this something that the community
> would be interested in having.
> 
> Thanks,
> 
> Brian
>
> This email and any information disclosed in connection
> herewith, whether written or oral, is the property of
> EnerNOC, Inc. and is intended only for the person or entity
> to which it is addressed.  
> This email may contain information that is privileged,
> confidential or otherwise protected from disclosure.  
> Distributing or copying any information contained in this
> email to anyone other than the intended recipient is
> strictly prohibited.