When you are designing a Column Families, so what makes you think for keeping the data in different column families 1. By Default each enity should be kept in different column family 2. Data that is not frequently accessed together should be kept in different Column Family 3. Data which used different compression methods 4. 1,2 and 3 are correct 5. Only 2 and 3 are correct
Correct Answer : 5
Explanation: Separate column families are useful for Data that is not frequently accessed together Data that uses different column family options e.g. compression
Question :
Select the correct option for HBase table 1. Physically stored on a per-column family basis. 2. Empty cells are not stored 3. Each cell has a timestamp 4. Multiple version of a cell can exist 5. All of the above
Correct Answer : 5
HBase tables are Physically stored on a per-column family basis Empty cells are not stored Each cell has a timestamp Multiple versions of a row can exist
Question :
When HBase is compared with RDBMS then which statement is true. 1. HBase automatically partitions data in regions 2. HBase does not support explicit joins 3. A lookup by row key implicitly joins data from column families if necessary 4. All of the above Solution : 15
Correct Answer : 4
Comparison with RDBMS design
Scaling relation tables often means partitioning or sharding data HBase automatically partitions data in regions In relational databases, one might normalize tables and use joins to retrieve data HBase does not support explicit joins A lookup by row key implicitly joins data from column families if necessary
Related Questions
Question : Please select the wrong statement regarding the Version delete 1. Deleting all the versions older than a certain timestamp can be performed on a row, column family or a column 2. Delete version at a specific timestamp and can only be performed on a column 3. For deletion if not timestamp is specified currentTimeMillis is used 4. For deletion if not timestamp is specified all the versions will be deleted
1. get 't1', 'r1' 2. get 't1', 'r1', {COLUMN => 'fam1:c1'} 3. get 't1', 'r1', {COLUMN => 'fam1:c1', VERSIONS=> 2} 4. All of the above
Question : Which statement is wrong about HBase 1. Tables can have thousands of columns 2. It is not mendatory to have dat data in all the columns 3. It does not support transaction 4. All of the above 5. None of the above