[
https://issues.apache.org/jira/browse/HIVE-26144?focusedWorklogId=757628&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-757628
]
ASF GitHub Bot logged work on HIVE-26144:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 16/Apr/22 21:37
Start Date: 16/Apr/22 21:37
Worklog Time Spent: 10m
Work Description: kovjanos commented on PR #3214:
URL: https://github.com/apache/hive/pull/3214#issuecomment-1100758580
That doesn't work with Oracle, even plain table has uniqueness issues - see
below. Do we need to have this also on ORACLE? I can add the column to keep
schema consistent, but it can't be a PRIMARY KEY (might not even be required
for the DELETEs in Oracle if it works differently).
One solution might be the old-school solution: a sequence and trigger behind
the increment column. I'll give it a try..
```
CREATE TABLE TEST_TABLE (
ID number(19) NOT NULL,
DB varchar(10) NOT NULL,
PKEY NUMBER(19) GENERATED ALWAYS AS IDENTITY
) ROWDEPENDENCIES;
INSERT ALL
INTO TEST_TABLE (ID, DB) VALUES (1,'1-db')
INTO TEST_TABLE (ID, DB) VALUES (2,'2-db')
INTO TEST_TABLE (ID, DB) VALUES (3,'3-db')
SELECT 1 FROM DUAL;
SELECT * FROM TEST_TABLE;
ID DB PKEY
--
Issue Time Tracking
-------------------
Worklog Id: (was: 757628)
Time Spent: 40m (was: 0.5h)
> 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: 40m
> 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.1#820001)
