Yes you can have the same CF name in different tables. Column Family
names are embedded in each KeyValue.
See: http://hbase.apache.org/book.html#regions.arch for more detail
It depends on what you you need. A common pattern is using composite keys
where the lead portion represents some natural grouping of data (e.g., a
userid) but that is also hashed to provide distribution across the cluster.
Read the RefGuide!
On 7/11/12 3:16 PM, "grashmi13" <[EMAIL PROTECTED]> wrote:
>In RDBMS we have multiple DB schemas\oracle user instances.
>Similarly, can we have multiple db schemas in hbase? If yes, can we have
>multiple schemas one one hadoop-hbase cluster? If multiple schemas
>how can we define them? Using configuration or programatically?
>Q2: can we have same column family name in multiple tables? if yes, does
>impacts performance if we have same name column family in multiple tables?
>Q3: Sequential keys improves read performance and random keys improves
>performance. which way one must go?
>Q4: What are best practices to improve hadoop+hbase performance?
>Q5: when one program is deleting tables, another program is accessing a
>of that table. what would be impact of it? can we have some sort of lock
>while reading or while deleting a table?
>Q6: as everything in application is byte form, what would happen if hbase
>and application are using different character set? can we synch both for
>some particular character set by configuration or programatically?
>View this message in context:
>Sent from the HBase User mailing list archive at Nabble.com.