You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Alexander Kolbasov (JIRA)" <ji...@apache.org> on 2017/12/07 22:50:00 UTC
[jira] [Updated] (HIVE-18247) Use DB auto-increment for indexes
[ 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)