hbase-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Edward Capriolo <edlinuxg...@gmail.com>
Subject Re: HBase Design Considerations
Date Mon, 03 May 2010 14:14:11 GMT
On Mon, May 3, 2010 at 4:04 AM, Steven Noels <stevenn@outerthought.org>wrote:

> On Mon, May 3, 2010 at 8:42 AM, Saajan <ssangraula@veriskhealth.com>
> wrote:
>
> Would highly appreciate comments on how HBase is used to support search
> > applications and how we can support search / filter across multiple
> > criteria
> > in HBase.
> >
>
> Hi,
>
> we were facing the same challenges during the Lily design, and decided to
> build an integration between HBase and SOLR (and use an HBase-based WAL for
> async operations against SOLR in a durable fashion). I realize this isn't
> entirely helpful here and now (we're currently shooting for a prerelease
> date of mid July), but your requirements seem to match closely what we are
> building at the moment.
>
> Lily sources will be released under an Apache license from www.lilycms.org
>
> Cheers,
>
> Steven.
> --
> Steven Noels                            http://outerthought.org/
> Outerthought                            Open Source Java & XML
> stevenn at outerthought.org             Makers of the Daisy CMS
>

A simple alternative to secondary indexes is to store the table a second
time:

Key -> Value
and
Value -> Key

With this design you can search on the key or the value quickly. With this,
a single insert is transformed into multiple inserts and keeping data
integrity falls on the user.

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