[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: -- Status: Patch Available (was: Open) > 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 >Priority: Major > Labels: datanucleus, perfomance > Attachments: HIVE-18247.02.patch > > > 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 (v7.6.3#76005)
[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: -- Attachment: HIVE-18247.02.patch > 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 >Priority: Major > Labels: datanucleus, perfomance > Attachments: HIVE-18247.02.patch > > > 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 (v7.6.3#76005)
[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: -- Status: Open (was: Patch Available) > 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 >Priority: Major > 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 (v7.6.3#76005)
[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: -- Attachment: (was: HIVE-18247.01.patch) > 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 >Priority: Major > 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 (v7.6.3#76005)
[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: -- Attachment: HIVE-18247.01.patch > 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 >Priority: Major > Labels: datanucleus, perfomance > Attachments: HIVE-18247.01.patch > > > 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 (v7.6.3#76005)
[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: -- Status: Patch Available (was: Open) > 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 >Priority: Major > Labels: datanucleus, perfomance > Attachments: HIVE-18247.01.patch > > > 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 (v7.6.3#76005)
[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: -- Attachment: (was: HIVE-18247.01.patch) > 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 >Priority: Major > 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 (v7.6.3#76005)
[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: -- Status: Open (was: Patch Available) > 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 >Priority: Major > 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 (v7.6.3#76005)
[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: -- Status: Patch Available (was: Open) > 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 > Attachments: HIVE-18247.01.patch > > > 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)
[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: -- Attachment: HIVE-18247.01.patch > 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 > Attachments: HIVE-18247.01.patch > > > 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)
[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)
