Return-Path: 
 <dev-return-28427-apmail-hbase-dev-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-dev-archive@www.apache.org
Delivered-To: apmail-hbase-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 388B696AB
	for <apmail-hbase-dev-archive@www.apache.org>;
 Sat, 26 May 2012 22:33:50 +0000 (UTC)
Received: (qmail 12928 invoked by uid 500); 26 May 2012 22:33:47 -0000
Delivered-To: apmail-hbase-dev-archive@hbase.apache.org
Received: (qmail 12742 invoked by uid 500); 26 May 2012 22:33:47 -0000
Mailing-List: contact dev-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hbase.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hbase.apache.org>
List-Post: <mailto:dev@hbase.apache.org>
List-Id: <dev.hbase.apache.org>
Reply-To: dev@hbase.apache.org
Delivered-To: mailing list dev@hbase.apache.org
Received: (qmail 12724 invoked by uid 99); 26 May 2012 22:33:47 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 22:33:47 +0000
X-ASF-Spam-Status: No, hits=-0.7 required=5.0
	tests=RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of saint.ack@gmail.com
 designates 209.85.216.50 as permitted sender)
Received: from [209.85.216.50] (HELO mail-qa0-f50.google.com) (209.85.216.50)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 26 May 2012 22:33:41 +0000
Received: by qafl39 with SMTP id l39so382046qaf.2
        for <multiple recipients>; Sat, 26 May 2012 15:33:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        bh=WrRDB1aA1WJ9Hin2vov747WTIUw9hSlpMz16lnYxuXw=;
        b=Z/TCUE2Ed9uRTb53ioGVK8PLT2hAylTUeiXOUOWV8mf2OcW+M7t3ruJv2upY6eWEky
         IUZ/fWv1wmnAJdWjBZFA15m+q8WWSLFc2VkM8t3SrSdnm32SgWlG5Qgn8n3ofRP4Ov9o
         yUS+t+9VX3qBQz0s9c41LCyaqqxmoblBBoUa+w7vYQxcnz25eEsgzeEG41kWKmJYaUQ+
         yCQ2d3Mi8SsgWCZOda+7C1sk6RFdBBt/nlb+tXtqukC24dglk0bnqxEF7RJRJzjwqdRM
         a/a+UuNubdmdNCyoVBTHvFI/8VC8lROnyyCy6uVGF8OhbNdv3N3kRzG2NRQyAYKuNqqq
         0j8A==
MIME-Version: 1.0
Received: by 10.229.134.200 with SMTP id k8mr949938qct.137.1338071600140; Sat,
 26 May 2012 15:33:20 -0700 (PDT)
Sender: saint.ack@gmail.com
Received: by 10.229.135.149 with HTTP; Sat, 26 May 2012 15:33:20 -0700 (PDT)
In-Reply-To: <4D637AA8-1406-4517-B38B-1FBEC6540028@gmail.com>
References: <1368342021.6360.1338067163890.JavaMail.jiratomcat@issues-vm>
	<4D637AA8-1406-4517-B38B-1FBEC6540028@gmail.com>
Date: Sat, 26 May 2012 15:33:20 -0700
X-Google-Sender-Auth: 5uLGX3Xheh0OiGyrDqctZacjjt0
Message-ID: 
 <CADcMMgFBb7VbBCeYDotjHvz2_-NJadaxMHiw3voZ-YfaPF+N4Q@mail.gmail.com>
Subject: Re: Rethinking REST (Re: HBASE-4368 and friends)
From: Stack <stack@duboce.net>
To: user@hbase.apache.org
Cc: "dev@hbase.apache.org" <dev@hbase.apache.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

On Sat, May 26, 2012 at 2:54 PM, Andrew Purtell
<andrew.purtell@gmail.com> wrote:
> Perhaps it's time to consider consolidating these interfaces on a single =
port, where they differ, and more generally re-embed REST into the processe=
s, like the recent Thrift server embedding in the RS? This would be a new a=
lternative to the current REST gateway that would function more like HDFS h=
ttpfs: a client can contact any RS with a RESTful operation on a table, and=
 it will be redirected via the HTTP standard mechanism to the RS actually h=
osting the target region. And beside such a client API, these admin functio=
ns like 4368 and the JMX export over HTTP we inherit from Hadoop core.
>

An integrated REST server could answer questions about the
regionserver it was on.  It could return list of regions and metrics
for the server.  +1.

Would the REST server above that answer queries on the regionserver be
the same as the REST server that we currently have which fields
queries against hbase tables?  They seem to be different things?

St.Ack