hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Kolbasov (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-18247) Use DB auto-increment for indexes
Date Thu, 07 Dec 2017 22:50:00 GMT

     [ https://issues.apache.org/jira/browse/HIVE-18247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Kolbasov updated HIVE-18247:
--------------------------------------
    Labels: datanucleus perfomance  (was: )

> Use DB auto-increment for indexes
> ---------------------------------
>
>                 Key: HIVE-18247
>                 URL: https://issues.apache.org/jira/browse/HIVE-18247
>             Project: Hive
>          Issue Type: Bug
>          Components: Hive, Metastore
>    Affects Versions: 3.0.0
>            Reporter: Alexander Kolbasov
>            Assignee: Alexander Kolbasov
>              Labels: datanucleus, perfomance
>
> I initially noticed this problem in Apache Sentry - see SENTRY-1960. Hive has the same
issue. DataNucleus uses SEQUENCE table to allocate IDs which requires raw locks on multiple
tables during transactions and this creates scalability problems. 
> Instead DN should rely on DB auto-increment mechanisms which are much more scalable.
> See SENTRY-1960 for extra details.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message