[
https://issues.apache.org/jira/browse/HIVE-17830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16209639#comment-16209639
]
Thejas M Nair commented on HIVE-17830:
--------------------------------------
[~anishek]
Looking at metastore direct sql code, it looks like select can be common across
dbs -
metastoredirect sql does seem to use quoted column names, but not quoted table
name -
eg -
MetaStoreDirectSQL.java -
{code}
String queryTextDbSelector= "select "
+ "\"DB_ID\", \"NAME\", \"DB_LOCATION_URI\", \"DESC\", "
+ "\"OWNER_NAME\", \"OWNER_TYPE\" "
+ "FROM "+ DBS +" where \"NAME\" = ? ";
{code}
> 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: anishek
> Priority: Critical
> Fix For: 3.0.0
>
> Attachments: HIVE-17830.0.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)
