You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@hive.apache.org by "Stamatis Zampetakis (Jira)" <ji...@apache.org> on 2022/04/16 14:41:00 UTC

[jira] [Commented] (HIVE-26144) Add keys/indexes to support highly concurrent workload

    [ https://issues.apache.org/jira/browse/HIVE-26144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17523115#comment-17523115 ] 

Stamatis Zampetakis commented on HIVE-26144:
--------------------------------------------

Hey [~kovjanos], can you please provide more details on which are the problematic queries and how the *new* primary key fields will speed those up?

In general, adding indexes and constraints tends to make lookup queries faster but at the same time DML queries (INSERT, UPDATE, DELETE) slower. Are the benchmarks you performed representative of various use-cases? 

> 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: 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.1#820001)