[
https://issues.apache.org/jira/browse/HIVE-14047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eugene Koifman reassigned HIVE-14047:
-------------------------------------
Assignee: Steve Yeom
> add primary key on WRITE_SET
> ----------------------------
>
> Key: HIVE-14047
> URL: https://issues.apache.org/jira/browse/HIVE-14047
> Project: Hive
> Issue Type: Bug
> Components: Transactions
> Affects Versions: 1.3.0, 2.1.0
> Reporter: Thejas M Nair
> Assignee: Steve Yeom
>
> WRITE_SET table created in HIVE-13395 should some columns in the primary key.
> I expect most databases to organize the data in a b-tree with primary key as
> the index (or have an option to do so). That should help in reducing the
> search space for your prominent queries. As long as columns in the where
> clause match the prefix of the index, it should greatly reduce the search
> space.
> You can add a autoincrement column to keep it unique if necessary. MySQL
> (innodb) anyway ends up organizing data on an autoincrement column, which is
> useless for the queries (see post ).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
