[
https://issues.apache.org/jira/browse/TRAFODION-1423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14652637#comment-14652637
]
ASF GitHub Bot commented on TRAFODION-1423:
-------------------------------------------
Github user zellerh commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/37#discussion_r36137159
--- Diff: core/sql/optimizer/NAFileSet.h ---
@@ -72,6 +72,13 @@ enum FileOrganizationEnum
KEY_SEQUENCED_FILE,
HASH_FILE
};
+
+enum RowFormatEnum {
+ SQLMX_UNKNOWN_FORMAT,
+ SQLMX_ROW_FORMAT,
+ SQLMX_ALIGNED_ROW_FORMAT,
+ SQLMX_HBASE_FORMAT
--- End diff --
SQLMX_ALIGNED_ROW_FORMAT is already used in NATable.h for a flag. Should we
avoid this conflict (renaming either one). Also, I'm wondering whether this
should go into ComSmallDefs, since it is fairly fundamental.
> Indexes on trafodion should be created in aligned row format by default
> -----------------------------------------------------------------------
>
> Key: TRAFODION-1423
> URL: https://issues.apache.org/jira/browse/TRAFODION-1423
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: sql-cmp, sql-cmu
> Affects Versions: 2.0-incubating
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> Currently indexes are created with the same row format as the table. However,
> indexes can be created in aligned row format independent of the table because
> the columns in the index table doesn't have any other column other than salt,
> index columns, and primary key of the table. These column values constitute
> the rowid. Index rows are always deleted and inserted and are never updated.
> Hence, it goes well to create index in aligned row format. In addition, index
> in aligned row format has the following advantages:
> - Reduced storage space for the index
> - Reduced block cache and memstore space at runtime
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
