Home | About | Sematext search-lucene.com search-hadoop.com
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB
 Search Hadoop and all its subprojects:

Switch to Threaded View
HBase >> mail # user >> Expert suggestion needed to create table in Hbase - Banking


Copy link to this message
-
Re: Expert suggestion needed to create table in Hbase - Banking
More on number of column families:
http://hbase.apache.org/book/number.of.cfs.html
On Sun, Nov 25, 2012 at 11:35 PM, anil gupta <[EMAIL PROTECTED]> wrote:

> Hi Rams,
>
> The description of your use case is very abstract so i will try to answer
> your question to the best of my ability.
>
>
> 1) Whether is it good to create a single table for all the 600+ columns?
> Anil: Yes, it is absolutely ok to have 600+ columns in a row in HBase (you
> can go max upto few millions)
>
>
> 2) To have different column families for different groups or can it be
> under a single column family? For example, customer address can we have as
> a different column family?
> Anil: Usually HBase recommends not to have many column families(not more
> than 3 or 4). Having one column family is a very standard practice.
> However, in some cases creating more then one CF is justified. For example
> in around 95% of your lookups if you dont need to access "Customer Address"
> data then it would make sense to put them into a separate column family.
>
> HTH,
> Anil Gupta
>
>
>
>
>
>
>
> On Sun, Nov 25, 2012 at 11:04 PM, Ramasubramanian Narayanan <
> [EMAIL PROTECTED]> wrote:
>
>> Hi,
>>
>>   I have a requirement of physicalising the logical model... I have a
>> client model which has 600+ entities...
>>
>>   Need suggestion how to go about physicalising it...
>>
>>   I have few other doubts :
>>   1) Whether is it good to create a single table for all the 600+ columns?
>>   2) To have different column families for different groups or can it be
>> under a single column family? For example, customer address can we have as
>> a different column family?
>>
>>   Please help on this..
>>
>>
>> regards,
>> Rams
>>
>
>
>
> --
> Thanks & Regards,
> Anil Gupta
>

--
Thanks & Regards,
Anil Gupta
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB