You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "anishek (JIRA)" <ji...@apache.org> on 2017/10/04 09:10:00 UTC
[jira] [Commented] (HIVE-17614) Notification_sequence
initialization using SQL statement which is compatible with Mysql 5.1
[ https://issues.apache.org/jira/browse/HIVE-17614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16191013#comment-16191013 ]
anishek commented on HIVE-17614:
--------------------------------
Patch committed to master, Thanks for review [~thejas]
> Notification_sequence initialization using SQL statement which is compatible with Mysql 5.1
> -------------------------------------------------------------------------------------------
>
> Key: HIVE-17614
> URL: https://issues.apache.org/jira/browse/HIVE-17614
> Project: Hive
> Issue Type: Improvement
> Components: HiveServer2
> Affects Versions: 3.0.0
> Reporter: anishek
> Assignee: anishek
> Fix For: 3.0.0
>
> Attachments: HIVE-17614.0.patch
>
>
> Since a lot of people are still using hive with 5.1 mysql as the rdbms for metastore, it will be helpful to have the initialization statement introduced as part of HIVE-16886 for mysql to be friendlier to these older versions.
> INSERT INTO `NOTIFICATION_SEQUENCE` (`NNI_ID`, `NEXT_EVENT_ID`) SELECT * from (select 1 as `NNI_ID`, 1 as `NOTIFICATION_SEQUENCE`) a WHERE (select count(*) from `NOTIFICATION_SEQUENCE`) = 0;
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)