InvisibleProgrammer commented on PR #4949: URL: https://github.com/apache/hive/pull/4949#issuecomment-1857557428
> @InvisibleProgrammer Thanks for the comment. I have seen this behaviour wherein the NOTIFICATION_SEQUENCE table had multiple records and this pretty much messed up the notification log functionality which can spiral into an ugly situation in Hive clusters with an ugly workaround (deleting the record manually in this table). As a long term solution, I had added the one-row constraint on the NOTIFICATION_SEQUENCE table in [HIVE-26324](https://issues.apache.org/jira/browse/HIVE-26324). Unfortunately, one solution on MySQL didn't work on the MariaDB database. Hence I am making it consistent in this PR. Got it, thx. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
