Can you elaborate about this approach ? specially how can I ask queries like : give me all entities that has attribute a1 with value v1 (and attribute a2 with value v2)...
-- Yonatan On Sun, Dec 21, 2008 at 4:07 PM, Thibaut_ <[email protected]> wrote: > > Hi, > > just as a temporary fix, you could also use something like google protocol > buffers or facebook's thrift for the data modelling and only save the > binary > output in hbase. > > You will however loose the ability to filter on columns or only fetch the > columns you are interested in, and must always fetch all of the data > related > to an entity. > > Thibaut > > > yonatan maman wrote: > > > > I want to have to use HBAse to implement > > (Entity-attribute-value_model< > http://en.wikipedia.org/wiki/Entity-attribute-value_model>), > > in RDBM it looks like : > > > > col1: entityID > > > > col2: attributeName > > > > col3: value > > > > > > Will it be reasoniable to have one Hbase table like this: > > > > entityID as row key > > attr as column family > > > > so suppose I have 2 entities: > > e1: has 2 attibutes: a1 with value v1 and a2 with value v2 > > e2: has 2 attibutes: a1 wuth value v11 and a3 with value v33 > > > > > > e1--->attr:a1=v1, attr:a2=v2 > > e2--->attr:a1=v11, attr:a3=v33 > > > > I guess the number of different sohuld be low hundred (as suggested by > > stack). will this 'bug' taken care now ? what will be the limit wfter it > > will be fixed ? > > > > -- Yonatan > > > > > > > > > > > > > > On Sun, Dec 21, 2008 at 1:23 AM, Ryan LeCompte <[email protected]> > wrote: > > > >> Ah darn, I was just trying to experiment changing my schema to support > >> 1000's of columns.... however once I did that I started running out of > >> memory again. :-( > >> > >> > >> On Sat, Dec 20, 2008 at 6:19 PM, stack <[email protected]> wrote: > >> > yonatan maman wrote: > >> >> > >> >> I'm about to design my HBase table, and I wonder : > >> >> 1) what is the max number of column family that is still consider > >> >> reasonable? 100 , 1K, 1M ... more ? > >> >> > >> > > >> > Keep it small I'd say for now until we do more work in server > >> parallellizing > >> > querying of different column families. I'd suggest low tens. > >> > > >> >> 2) what is a reasonable number of columns per column family ? 100, > 1K > >> , > >> >> 1M > >> >> .. more ? > >> > > >> > Low hundreds till we fix the bug that has us slow when lots of > columns. > >> > > >> > St.Ack > >> > > >> > > >> > > > > > > -- > View this message in context: > http://www.nabble.com/what-is-considered-as-best---worst-practice--tp21109754p21115358.html > Sent from the HBase User mailing list archive at Nabble.com. > >
