Ramasubramanian Narayanan... 2013-06-04, 16:43
Shahab Yunus 2013-06-04, 16:51
Michel Segel 2013-06-04, 17:13
Ramasubramanian Narayanan... 2013-06-04, 17:22
Ian Varley 2013-06-04, 17:30
Michael Segel 2013-06-04, 18:47
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
create mutiple small HBASE tables where it has the read access pattern
columns and the rowkey it is mapped to the master table...
*Master Table :*
On Tue, Jun 4, 2013 at 12:51 PM, Shahab Yunus <[EMAIL PROTECTED]>wrote:
> 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 is not the case then I think why not take advantage of more
> On Tue, Jun 4, 2013 at 12:43 PM, Ramasubramanian Narayanan <
> [EMAIL PROTECTED]> wrote:
> > Hi,
> > In a HBASE table, there are 200 columns and the read pattern for
> > 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 rowkey? (something called
> > secondary index)
> > regards,
> > Rams