Re: schema design: rows vs wide columns

@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I recommend we strike it. We

Re: schema design: rows vs wide columns

Purtell apurt...@apache.org To: user@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book

Re: schema design: rows vs wide columns

@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I recommend we strike it. We could replace

Re: schema design: rows vs wide columns

: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I recommend we strike it. We could replace it with YCSB

Re: schema design: rows vs wide columns

apurt...@apache.org To: user@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I

Re: schema design: rows vs wide columns

StAck, Just because FB does something doesn't mean its necessarily a good idea for others to do the same. FB designs specifically for their needs and their use cases may not match those of others. To your point though, I agree that Ted's number of 3 is more of a rule of thumb and not a

Re: schema design: rows vs wide columns

From: Andrew Purtell apurt...@apache.org To: user@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis

schema design: rows vs wide columns

Hello, I am newer for hbase, but i have some experience on cassandra. In the official document, it is said prefer to use rows instead of columns. I don't know whether I should follow. This is my user case: I have about hundreds of services. each service is stored by a number(service id). we try

Re: schema design: rows vs wide columns

If you store service Id by month, how do you deal with time range in query that spans partial month(s) ? With regard to number of column families, 3 is the recommended maximum. Cheers On Apr 7, 2013, at 1:03 AM, shawn du shawndow...@gmail.com wrote: Hello, I am newer for hbase, but i

Re: schema design: rows vs wide columns

On Sun, Apr 7, 2013 at 11:58 AM, Ted yuzhih...@gmail.com wrote: With regard to number of column families, 3 is the recommended maximum. How did you come up w/ the number '3'? Is it a 'hard' 3? Or does it depend? If the latter, on what does it depend? Thanks, St.Ack

Re: schema design: rows vs wide columns

From http://hbase.apache.org/book.html#number.of.cfs : HBase currently does not do well with anything above two or three column families so keep the number of column families in your schema low. Cheers On Sun, Apr 7, 2013 at 3:04 PM, Stack st...@duboce.net wrote: On Sun, Apr 7, 2013 at 11:58

Re: schema design: rows vs wide columns

On Sun, Apr 7, 2013 at 3:27 PM, Ted Yu yuzhih...@gmail.com wrote: From http://hbase.apache.org/book.html#number.of.cfs : HBase currently does not do well with anything above two or three column families so keep the number of column families in your schema low. We should add more to that

Re: schema design: rows vs wide columns

Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I recommend we strike it. We could replace it with YCSB or LoadTestTool driven latency graphs for different workloads maybe. Although that would also be a big

Re: schema design: rows vs wide columns

I think this whole idea of don't go over a certain number of column families was a 2+ year old story. I remember hearing numbers like 5 or 6 (not 3) come up when talking at Hadoop conferences with engineers who were at companies that were heavy HBase users. I agree with Andrew's suggestion that we

Re: schema design: rows vs wide columns

I agree with Andrew here and also Stack's comment on FB usage with 15 CFs is interesting. Whenever people read that line from the doc, people used to ask why is it so and also i was thinking that one restriction of having max 3 CFs was one factor which sometimes made schema design a bit

Re: schema design: rows vs wide columns

...@apache.org To: user@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer to evidence/experiment backed analysis of this question? I'm sure there is some basis for this text in the book but I recommend we strike

Re: schema design: rows vs wide columns

known that is bad about many column families? -- Lars From: Andrew Purtell apurt...@apache.org To: user@hbase.apache.org user@hbase.apache.org Sent: Sunday, April 7, 2013 3:52 PM Subject: Re: schema design: rows vs wide columns Is there a pointer