Hey,
I generally don't think of hbase entries like spreadsheets with 'nulls' in
the empty locations. Its really more like an adjacency list, where the data
is only there when it's there.
But I was referring to your create, the key is 'VERSIONS' not 'VERSION'.
create 'table', {NAME=>'family', VERSIONS=>1}
On Thu, May 21, 2009 at 11:35 PM, Edward J. Yoon <[email protected]>wrote:
> Let's assume, there are two 2 * 2 sparse tables as below.
>
> t1
> ----
> null 2
> -1 null
>
> t2
> ----
> -3 null
> null null
>
> I'll put these tables to table 'x'. And, The table 'x' will handle
> only one version. Then, 't2' should be appeared, not 't1' + 't2'
> table.
>
> Currently, Hbase shows the 't1' + 't2' table as below.
> ----
> -3(t2) 2(t1)
> -1(t1) null (what is this?)
>
> Should I update the all 't1' entries?
>
> On Fri, May 22, 2009 at 3:11 PM, Ryan Rawson <[email protected]> wrote:
> > The key is 'VERSIONS'. Give it another shot.
> >
> > -ryan
> >
> > On Thu, May 21, 2009 at 11:07 PM, Edward J. Yoon <[email protected]
> >wrote:
> >
> >> hbase(main):001:0> create 't1', {NAME=> 'f1', VERSION => 1}
> >> hbase(main):002:0> put 't1', 'r1', 'f1' ,'value', 1
> >> hbase(main):007:0> put 't1', 'r2', 'f1:' ,'value', 2
> >>
> >> I made a table 't1' as above. And, When scan this,
> >>
> >> hbase(main):008:0> scan 't1'
> >> ROW COLUMN+CELL
> >> r1 column=f1:, timestamp=1, value=value
> >> r2 column=f1:, timestamp=2, value=value
> >> 2 row(s) in 0.0330 seconds
> >>
> >> I expected only one row 'r2' (sparse table for time t2) but there are
> >> two tables on time dimension. I think it's a logical bug. The 't1'
> >> should maintain only one version of time dimension table.
> >>
> >> What do you think?
> >> --
> >> Best Regards, Edward J. Yoon @ NHN, corp.
> >> [email protected]
> >> http://blog.udanax.org
> >>
> >
>
>
>
> --
> Best Regards, Edward J. Yoon @ NHN, corp.
> [email protected]
> http://blog.udanax.org
>
