Re: Number of tables in HBase.

Having dozens of tables in a multi-tenant cluster is okay. How many regions on average would each table have ? The total number of regions should have higher weight in your planning compared to the total number of tables. Cheers > On Jan 18, 2016, at 4:19 AM, Guillermo Ortiz wr

Re: Number of tables in HBase.

Sorry, I mean just few column families,, 1 to 3 column families. But I don't know if it's a good idea to have too many tables in HBase. 2016-01-18 11:15 GMT+01:00 Guillermo Ortiz : > Hello, > > I know that a table should have a content number of CFs. How about the > number

Number of tables in HBase.

Hello, I know that a table should have a content number of CFs. How about the number of tables in the same HBase cluster? it should be okay to have dozens of tables or it's thought to have just a few number of tables?

Re: restriction on the number of tables in hbase and its impact on performance

r wrote: > I have asked this question on stackoverflow - > > http://stackoverflow.com/questions/12066856/restriction-on-the-number-of-tables-in-hbase-and-its-impact-on-performance > > Also asking the same on this list -- > > Our hbase schema in production has 5 tables. We have

Re: Maximum number of tables ?

gt; >>> The question here is - why do you need to distribute your data over > >>> lots of tables? What's your access pattern and what kind of data are > >>> you putting in? Or is this just a theoretical question? > >>> > >>> On Jul 13

Re: Maximum number of tables ?

>>> The question here is - why do you need to distribute your data over >>> lots of tables? What's your access pattern and what kind of data are >>> you putting in? Or is this just a theoretical question? >>> >>> On Jul 13, 2012, at 12:05 AM, Adrie

Re: Maximum number of tables ?

> On Jul 13, 2012, at 12:05 AM, Adrien Mogenet >> wrote: >> >>> Hi there, >>> >>> I read some good practices about number of columns / column families, but >>> nothing about the number of tables. >>> What if I need to spread my da

Re: Maximum number of tables ?

: > > > Hi there, > > > > I read some good practices about number of columns / column families, but > > nothing about the number of tables. > > What if I need to spread my data among hundred or thousand (big) tables ? > > What should I care about ?

Re: Maximum number of tables ?

stion? On Jul 13, 2012, at 12:05 AM, Adrien Mogenet wrote: > Hi there, > > I read some good practices about number of columns / column families, but > nothing about the number of tables. > What if I need to spread my data among hundred or thousand (big) tables ? > What should I

Re: Maximum number of tables ?

Jul 13, 2012 at 9:04 AM, Adrien Mogenet > wrote: >> Hi there, >> >> I read some good practices about number of columns / column families, but >> nothing about the number of tables. >> What if I need to spread my data among hundred or thousand (big) table

Re: Maximum number of tables ?

n' will go to a single table. And so on. N. On Fri, Jul 13, 2012 at 9:04 AM, Adrien Mogenet wrote: > Hi there, > > I read some good practices about number of columns / column families, but > nothing about the number of tables. > What if I need to spread my data among hu

Re: Number of tables

As far as we are concerned a user can only search once per second, view a product once per second, etc so the keys are unique. If we were going to be extra paranoid I suppose we could use epoch in ms instead of seconds to ensure this constraint. On 8/26/11 3:40 AM, Sheng Chen wrote: Hi, Mark,

Re: Number of tables

Hi, Mark, just follow your question. How do you make sure the uniqueness of the row key #{type}/#{user}/#{time}? If the action logs are generated from different app servers, it is possible to have several actions with the same type/user and timestamp. Thanks. Sean 2011/8/21 Mark > We are loggin

Re: Number of tables

Mark, Looks like you have your key setup correctly... What happens if you make your user as the first element in the key? You can go with multiple tables. This may also help to improve performance too. Sent from a remote device. Please excuse any typos... Mike Segel On Aug 21, 2011, at 1:34

Re: Number of tables

> Is there a disadvantage to create more tables? Not on the HBase side, in the end it's all regions. J-D

Re: Number of tables

About a million rows per day per table. Is there a disadvantage to create more tables? On 8/21/11 10:49 AM, Sonal Goyal wrote: If your data size is big enough to warrant 3 tables, go for it. This would be the case where there are really lots of entries for user#type. Best Regards, Sonal Crux:

Re: Number of tables

If your data size is big enough to warrant 3 tables, go for it. This would be the case where there are really lots of entries for user#type. Best Regards, Sonal Crux: Reporting for HBase Nube Technologies

Re: Number of tables

Almost all use cases require type.. ie Retrieve all searches performed by user 'foo': scan "history", {STARTROW => "search/foo"} Retrieve all product views performed by user 'foo': scan "history", {STARTROW => "view/foo"} On 8/21/11 10:25 AM, Sonal Goyal wrote: Hi Mark, When you say that y

Re: Number of tables

Hi Mark, When you say that your use case does not require searching across multiple types, what do you mean? Do you have cases when you search with type? Best Regards, Sonal Crux: Reporting for HBase Nube Technologies

Number of tables

We are logging all user actions into hbase. These actions include searches, product views and clicks. We are currently storing them in one table with row keys like so: "#{type}/#{user}/#{time}", where type is either click, search, view and user is the current user logged in. Obviously using th