I can align with putting it into the rest endpoint if we agree on that exposing
it is not a problem.
Janos
On 12/25/17, 6:46 AM, "stack" <saint....@gmail.com> wrote:
REST endpoint more natural loci for programmatic consumers imo
On Dec 24, 2017 5:22 PM, "Apekshit Sharma" <a...@cloudera.com> wrote:
> I started looking into more after last reply.
> I think exposing this info can be useful to the operators - dashboard of
> region states, or tools to quickly dump list of regions which require
care,
> etc
> But wasn't thinking about hbase rest api so far.
> I think web ui is not the right endpoint to expose json api when we
already
> have a whole well designed way to do it - REST apis.
> It should rather be an addition to Table endpoints (table 14 here:
> http://hbase.apache.org/book.html#_using_rest_endpoints).
>
> -- Appy
>
> On Sun, Dec 24, 2017 at 5:16 PM, Apekshit Sharma <a...@cloudera.com>
> wrote:
>
> > More details:
> > Proposed interface is json.
> > Pros:
> > - more info exposed to operators, can be used for scripting
> >
> > Cons:
> > - We don't have functions in Admin to expose region states
> > - We don't expose much programatic info through our web ui.
> >
> > -- Appy
> >
> >
> >
> > On Fri, Dec 22, 2017 at 6:01 PM, Ted Yu <yuzhih...@gmail.com> wrote:
> >
> >> Hi,
> >> See (tail of) HBASE-17436 for detailed background information.
> >>
> >> Here is the summary:
> >>
> >> In HBASE-17436 (and HBASE-19594), region state is accessed thru web UI.
> >> This is for helping operators gain better insight into the cluster
> status.
> >>
> >> However, since RegionState is marked @InterfaceAudience.Private , we
> (Appy
> >> and I) want to present this discussion to the community to raise
> >> awareness.
> >>
> >> Your comment is welcome.
> >>
> >
> >
> >
> > --
> >
> > -- Appy
> >
>
>
>
> --
>
> -- Appy
>
