[
https://issues.apache.org/jira/browse/TRAFODION-1419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14662346#comment-14662346
]
ASF GitHub Bot commented on TRAFODION-1419:
-------------------------------------------
GitHub user anoopsharma00 opened a pull request:
https://github.com/apache/incubator-trafodion/pull/48
[TRAFODION-1419] Support for multiple column families in traf table
details in jira
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/anoopsharma00/incubator-trafodion fix1
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-trafodion/pull/48.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #48
----
commit 674f4303615b169c170dfe0dc95084139855b12d
Author: Anoop Sharma <[email protected]>
Date: 2015-07-16T23:55:26Z
commit #1
commit 1ab11c164951cd83528bab7e3174b97e09c9e30b
Author: Anoop Sharma <[email protected]>
Date: 2015-07-17T14:50:33Z
Merge remote branch 'origin/master' into fix1
Conflicts:
core/sql/sqlcomp/DefaultConstants.h
commit 1fbe49085def2e23b57388b76f7548aefc823214
Author: Anoop Sharma <[email protected]>
Date: 2015-07-19T17:54:11Z
commit #2
commit 3456b64192335bf13cee14ae9890439d236d797d
Author: Anoop Sharma <[email protected]>
Date: 2015-07-20T00:10:15Z
commit #3
commit 235653a9c61c891b65cd28230336e23ae87e42dd
Author: Anoop Sharma <[email protected]>
Date: 2015-07-27T16:19:37Z
commit #4
commit 7c229c9b71101cf0e47ba9381bd543896a1442c9
Author: Anoop Sharma <[email protected]>
Date: 2015-08-03T20:34:53Z
Merge remote branch 'origin/master' into fix1
Conflicts:
core/sql/sqlcomp/DefaultConstants.h
commit cfa1bede6d1dc0be0943f4545773641afda2bb8c
Author: Anoop Sharma <[email protected]>
Date: 2015-08-06T15:24:34Z
commit #5
commit 747ca0cf0cbd0023e97eb380ad621cb22c569687
Author: Anoop Sharma <[email protected]>
Date: 2015-08-06T15:30:49Z
Merge remote branch 'origin/master' into fix1
Conflicts:
core/sql/comexe/ComTdb.h
commit 65964bd2aef6419ed3a661ca84854e96dcac50d9
Author: Anoop Sharma <[email protected]>
Date: 2015-08-07T16:43:32Z
commit #6
commit 8761da5384b7bf11c119d4cadec2cd7c5c17ffae
Author: Anoop Sharma <[email protected]>
Date: 2015-08-07T20:01:58Z
commit #7
----
> Add support for multiple column families in a trafodion table
> -------------------------------------------------------------
>
> Key: TRAFODION-1419
> URL: https://issues.apache.org/jira/browse/TRAFODION-1419
> Project: Apache Trafodion
> Issue Type: New Feature
> Reporter: Anoop Sharma
> Assignee: Anoop Sharma
>
> This proposal is to add support for multiple column families in trafodion
> tables. With this feature, one can store columns into multiple column
> families. One use for this would be to store frequently used columns in one
> column family and infrequently used columns to be stored in a different
> column family. That will have performance improvement when those columns are
> retrieved from hbase. There could be other uses as well.
> Syntax:
> create table <tablename> ( <colFam1>.<colName1> <datatype>,
> <colFam2>.<colName2> <datatype> ….)
> attributes default column family <colFam>;
> alter table <tablename> add column <colFam>.<colName> datatype;
> <colFam> : name of column family for that column
> Semantics:
> <colFam> name follows identifier rules. If not double quoted, then it
> will be upper cased. If double quoted, then case will be maintained.
> User specified column family can be of arbitrary length. To optimize
> space for column family stored in a cell, a 2 byte encoding is generated.
> Mapping of user specified column family to encoded column family is stored in
> metadata.
> If no column family is specified for a column during create table, then
> the family specified in ‘attributes default column family’ clause is used.
> If no ‘attribute default column family’ clause is specified , then system
> default col family is used.
> column family specification is supported for regular and volatile
> tables.
> all unique column families specified during create or alter are added
> to the table
> maximum number of column families supported in one table is 32. But it
> is hbase recommendation to not create too many column families.
> alter statement can be used to assign specific hbase options to
> specific column families
> using the NAME clause. If no name clause is specified, then alter hbase
> options are applied
> to all col families.
> invoke and showddl statements will show the original user specified
> column families and not the encoded column families
> Currently, multiple column families are not supported for columns of a
> user created or an implicitly created index.
> The default column family of the corresponding base table is used for all
> index columns.
> column family cannot be specified in a DML query
> column family cannot be specified for columns of an aligned row format
> table since all columns are stored as one cell
> Column names must be unique for each table. The same column name cannot
> be used as part of multiple column families.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
