You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Daniel Dai (JIRA)" <ji...@apache.org> on 2017/12/18 23:54:00 UTC
[jira] [Commented] (HIVE-17830) dbnotification fails to work with
rdbms other than postgres
[ https://issues.apache.org/jira/browse/HIVE-17830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16295893#comment-16295893 ]
Daniel Dai commented on HIVE-17830:
-----------------------------------
Created HIVE-18299 for continuation work.
> dbnotification fails to work with rdbms other than postgres
> -----------------------------------------------------------
>
> Key: HIVE-17830
> URL: https://issues.apache.org/jira/browse/HIVE-17830
> Project: Hive
> Issue Type: Bug
> Components: HiveServer2
> Reporter: anishek
> Assignee: Daniel Dai
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HIVE-17830.0.patch, HIVE-17830.1.patch
>
>
> as part of HIVE-17721 we had changed the direct sql to acquire the lock for postgres as
> {code}
> select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for update;
> {code}
> however this breaks other databases and we have to use different sql statements for different databases
> for postgres use
> {code}
> select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" for update;
> {code}
> for SQLServer
> {code}
> select "NEXT_EVENT_ID" from "NOTIFICATION_SEQUENCE" with (updlock);
> {code}
> for other databases
> {code}
> select NEXT_EVENT_ID from NOTIFICATION_SEQUENCE for update;
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)