lassing/adapting region servers and
scanner API and Hbase shell commands for our ends.
Thanks again,
Andrew Purtell
Advanced Threats Research
Trend Micro, Inc, Pasadena, CA USA
(personal mail)
Be a better
Thank you all for your considered responses. I would like
to make a few comments and clarifications (inline, below).
Jim Kellerman wrote:
> > Andrew Purtell wrote:
> > First: How invasive to the HBase master/region model is
> > the concept of specifying constraints on data
> > changes, ideally there would be a HBase shell command
> > to support this.
Yes.
The bit about fixing key ranges was a nod to minor
application layer transparency (no need to code up region
aware logic to select separate tables, etc.) since I was
laying out a wish list.
Andrew
> stack <[EMAIL PROTECTED]> wrote:
> Andrew Purtell wrote:
[...]
> > 1) The ability to fix a given key range to a region.
> > This would both assign a range to a given region, and
> > also disable splitting over that range. Aside from API
> > changes, ideally
answers to two
questions.
First: How invasive to the HBase master/region model is the
concept of specifying constraints on data mobility?
Second: How difficult would the modifications may be to
accomplish?
I believe these questions to be related. :-)
Thanks,
Andrew Purtell
Advanced Threats Research
