[ https://issues.apache.org/jira/browse/TRAFODION-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hans Zeller resolved TRAFODION-52. ---------------------------------- Resolution: Duplicate > LP Blueprint: cmp-trafodion-to-hbase-mapping - Make the mapping of Trafodion > tables to HBase tables and column families more flexible > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: TRAFODION-52 > URL: https://issues.apache.org/jira/browse/TRAFODION-52 > Project: Apache Trafodion > Issue Type: New Feature > Components: sql-cmp > Reporter: Hans Zeller > Assignee: Hans Zeller > Priority: Minor > > Right now, each Trafodion table is mapped to an HBase table with one column > family. This could be a problem in the future, if a user creates very many > Trafodion tables. It is known that HBase is not designed to have a very high > number of tables and/or regions, due to the high memory footprint that is > caused by every region. > One solution could be to allow multiple Trafodion tables to share a single > HBase table, and to use a 2 byte table id as the key prefix to identify the > table. This would work only for small tables that don't need to be split into > regions and for tables that wouldn't create a hot spot. > One the other side, it may be desirable to separate frequently used columns > in large tables from those that are less frequently used. That could be > achieved by using more than one column family. > Both features - sharing common HBase tables and utilizing multiple column > families - would require new Trafodion SQL syntax. Given the complexity of > the DDL code, it would be a significant effort to implement these features. -- This message was sent by Atlassian JIRA (v6.3.15#6346)