Ok...
A little bit more detail...
First, its possible to store your data in multiple tables each with a different
key.
Not a good idea for some very obvious reasons
You could however create a secondary table which is an inverted table where the
rowkey of the index is the value in the base
Rams - you might enjoy this blog post from HBase committer Jesse Yates (from
last summer):
http://jyates.github.io/2012/07/09/consistent-enough-secondary-indexes.html
Secondary Indexing doesn't exist in HBase core today, but there are various
proposals and early implementations of it in flight.
Hi Michel,
If you don't mind can you please help explain in detail ...
Also can you pls let me know whether we have secondary index in HBASE?
regards,
Rams
On Tue, Jun 4, 2013 at 1:13 PM, Michel Segel wrote:
> Quick and dirty...
>
> Create an inverted table for each index
> Then you can t
Quick and dirty...
Create an inverted table for each index
Then you can take the intersection of the result set(s) to get your list of
rows for further filtering.
There is obviously more to this, but its the core idea...
Sent from a remote device. Please excuse any typos...
Mike Segel
On
Hi,
The read pattern differs from each application..
Is the below approach fine?
Create one HBASE table with a unique rowkey and put all 200 columns into
it...
create mutiple small HBASE tables where it has the read access pattern
columns and the rowkey it is mapped to the master table...
e.g
Just a quick thought, why don't you create different tables and duplicate
data i.e. go for demoralization and data redundancy. Is your all read
access patterns that would require 70 columns are incorporated into one
application/client? Or it will be bunch of different clients/applications?
If that
Hi,
In a HBASE table, there are 200 columns and the read pattern for diffferent
systems invols 70 columns...
In the above case, we cannot have 70 columns in the rowkey which will not
be a good design...
Can you please suggest how to handle this problem?
Also can we do indexing in HBASE apart from
