hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Dai (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HIVE-17830) dbnotification fails to work with rdbms other than postgres
Date Mon, 23 Oct 2017 06:52:00 GMT

    [ https://issues.apache.org/jira/browse/HIVE-17830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16214731#comment-16214731
] 

Daniel Dai commented on HIVE-17830:
-----------------------------------

Ok so "SET @@session.sql_mode=ANSI_QUOTES" will be required, right? Last time I read the code,
it seems prepareTxn will be invoked every time we created a new ObjectStore. However, I must
miss somewhere as otherwise, we will never hit the sql syntax error.

> 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)

Mime
View raw message