[
https://issues.apache.org/jira/browse/HIVE-26144?focusedWorklogId=779084&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-779084
]
ASF GitHub Bot logged work on HIVE-26144:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 07/Jun/22 13:17
Start Date: 07/Jun/22 13:17
Worklog Time Spent: 10m
Work Description: deniskuzZ commented on code in PR #3214:
URL: https://github.com/apache/hive/pull/3214#discussion_r891212351
##########
standalone-metastore/metastore-server/src/main/sql/derby/hive-schema-4.0.0-alpha-2.derby.sql:
##########
@@ -570,7 +571,8 @@ CREATE TABLE COMPLETED_TXN_COMPONENTS (
CTC_PARTITION varchar(767),
CTC_TIMESTAMP timestamp DEFAULT CURRENT_TIMESTAMP NOT NULL,
CTC_WRITEID bigint,
- CTC_UPDATE_DELETE char(1) NOT NULL
+ CTC_UPDATE_DELETE char(1) NOT NULL,
+ CTC_ID bigint PRIMARY KEY GENERATED BY DEFAULT AS IDENTITY
Review Comment:
oh, sorry that's not a TXN_ID column, might be worse to check `HIVE-23048:
Use sequences for TXN_ID generation`.
What are the problematic queries that could benefit from TC_ID/CTC_ID PK?
Issue Time Tracking
-------------------
Worklog Id: (was: 779084)
Time Spent: 2h 10m (was: 2h)
> Add keys/indexes to support highly concurrent workload
> ------------------------------------------------------
>
> Key: HIVE-26144
> URL: https://issues.apache.org/jira/browse/HIVE-26144
> Project: Hive
> Issue Type: Sub-task
> Components: Database/Schema
> Reporter: Janos Kovacs
> Assignee: Janos Kovacs
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> The following indexes are added to avoid full table-scan in backend rdbms:
> - primary key for COMPLETED_TXN_COMPONENTS
> - primary key for TXN_COMPONENTS
> - index for TXN_WRITE_NOTIFICATION_LOG
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
