Mailing-List: contact user-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@hbase.apache.org
Received-SPF: pass (nike.apache.org: domain of michael_segel@hotmail.com
 designates 65.55.111.96 as permitted sender)
Message-ID: <BLU0-SMTP2707A804074D0C6A8B2197C8F430@phx.gbl>
From: Michael Segel <michael_segel@hotmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Lets talk about joins...
Date: Tue, 20 Aug 2013 13:56:40 -0500
CC: "dev@hbase.apache.org" <dev@hbase.apache.org>
To: "user@hbase.apache.org" <user@hbase.apache.org>
MIME-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))


When you start looking at secondary indexing, they really become =
powerful when you want to join two tables.=20
(Something I thought was already being discussed....)=20

So you can use the inverted table as a secondary index with one small =
glitch...=20
And then create a table of indexes.  Where each row represents an index =
and the columns are the rowkeys in that index.=20
(Call it a foreign key table.)=20

Now for the glitch... what happens when your row exceeds the width of =
your region. ;-)=20
There's a solution for that. ;-)=20

The other issue would be asynchronous writes.=20

I figured that one should get the talk started now, rather than wait =
until later.=20

This is why you want secondary indexes., the other issue... theta joins =
but lets save that for later.

The opinions expressed here are mine, while they may reflect a cognitive =
thought, that is purely accidental.=20
Use at your own risk.=20
Michael Segel
michael_segel (AT) hotmail.com