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

Posted to issues@hive.apache.org by "Sourabh Badhya (Jira)" <ji...@apache.org> on 2022/06/14 06:13:00 UTC

[jira] [Updated] (HIVE-26324) Add "one-row-table" constraints on NOTIFICATION_SEQUENCE table

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

Sourabh Badhya updated HIVE-26324:
----------------------------------
    Description: NOTIFICATION_SEQUENCE table must have only record however there have been several reports of NOTIFICATION_SEQUENCE table having multiple records. In order to prevent this situation from happening, its best to enforce "one-row-table" constraints on NOTIFICATION_SEQUENCE table.  (was: NOTIFICATION_SEQUENCE table must have only record however there have been several reports of NOTIFICATION_SEQUENCE table having multiple records. In order to prevent this situation from happening its best to enforce "one-row-table" constraints on NOTIFICATION_SEQUENCE table.)

> Add "one-row-table" constraints on NOTIFICATION_SEQUENCE table
> --------------------------------------------------------------
>
>                 Key: HIVE-26324
>                 URL: https://issues.apache.org/jira/browse/HIVE-26324
>             Project: Hive
>          Issue Type: Bug
>            Reporter: Sourabh Badhya
>            Assignee: Sourabh Badhya
>            Priority: Major
>
> NOTIFICATION_SEQUENCE table must have only record however there have been several reports of NOTIFICATION_SEQUENCE table having multiple records. In order to prevent this situation from happening, its best to enforce "one-row-table" constraints on NOTIFICATION_SEQUENCE table.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)