You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Suresh Subbiah (JIRA)" <ji...@apache.org> on 2016/06/08 17:42:21 UTC
[jira] [Created] (TRAFODION-2042) Index shall inherit compression
and data_block_encoding HBase options from Table
Suresh Subbiah created TRAFODION-2042:
-----------------------------------------
Summary: Index shall inherit compression and data_block_encoding HBase options from Table
Key: TRAFODION-2042
URL: https://issues.apache.org/jira/browse/TRAFODION-2042
Project: Apache Trafodion
Issue Type: Improvement
Components: sql-general
Affects Versions: 2.0-incubating
Reporter: Suresh Subbiah
Assignee: Suresh Subbiah
When a an index is created on a Trafodion table using the CREATE INDEX statement, users accidentally omit specifying the HBASE_OPTIONS clause. This results in the index being uncompressed and occupying more than necessary space on disk. If the table is large this can also lead to errors during bulkload as a single region may have more than 32 HFiles each of size 10 GB (default max size for HFile created by bulkload).
Having the index inherit compression and encoding options used by the table by default is reasonable and will help.
If the user wishes for the index to have a different type of compression from the base table then it can be explicitly specified in the CREATE INDEX statement.
A CQD will also be provided to disable this attribute inheritance.
An attribute inherited from the base table will take precedence over compression/encoding type obtained from
HBASE_COMPRESSION_OPTION and HBASE_DATA_BLOCK_ENCODING_OPTION cqds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)