hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ted Yu <yuzhih...@gmail.com>
Subject Re: what's the roadmap of secondary index of hbase?
Date Tue, 01 Mar 2011 17:41:32 GMT
>> Some extra support in the master to colocate secondary index regions with
primary table regions is an interesting idea.
Google Megastore can embed index within the primary table.
If we can mark index rows, this approach would be feasible.

On Tue, Mar 1, 2011 at 9:14 AM, Andrew Purtell <apurtell@apache.org> wrote:

> > [Lars]
> > What is the reason not to use JDs replication WLA tracking (using ZK)
> > and add another "scope" like attribute to the coldefs to define the
> > indexing?
>
> This is similar to what I proposed in the original description on
> HBASE-3257 (
> http://mail-archives.apache.org/mod_mbox/hbase-issues/201011.mbox/%3C25844899.223551290369437343.JavaMail.jira@thor%3E
> )
>
> Regarding Dhruba's comment, using a table as a log+workqueue of secondary
> index updates is pretty much what Lily does:
> http://www.lilyproject.org/lily/about/playground/hbaserowlog.html
>
> Some extra support in the master to colocate secondary index regions with
> primary table regions is an interesting idea. The logic should be equally
> pluggable as that for (secondary) index key generators. Perhaps a
> balance/migration calculation with a pluggable term that can contribute some
> affinity given a list of regions already on the RS.
>
>    - Andy
>
>
>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message