[
https://issues.apache.org/jira/browse/HIVE-23033?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17061658#comment-17061658
]
Naveen Gangam edited comment on HIVE-23033 at 3/18/20, 12:01 PM:
-----------------------------------------------------------------
Thanks [~dlavati]. The patch for the branch-3 looks good.
Regarding the patch for master, I will get back to you on that. I want to
ensure that retro-fixing is ok in these scripts. Thanks again
edit: I just realized the new patch for master has been added as well. Patch
looks good in itself. I still want to double check before I +1 it. Thanks
was (Author: ngangam):
Thanks [~dlavati]. The patch for the branch-3 looks good.
Regarding the patch for master, I will get back to you on that. I want to
ensure that retro-fixing is ok in these scripts. Thanks again
> MSSQL metastore schema init script doesn't initialize NOTIFICATION_SEQUENCE
> ---------------------------------------------------------------------------
>
> Key: HIVE-23033
> URL: https://issues.apache.org/jira/browse/HIVE-23033
> Project: Hive
> Issue Type: Bug
> Affects Versions: 3.0.0, 3.1.0, 3.1.1, 3.1.2
> Reporter: David Lavati
> Assignee: David Lavati
> Priority: Major
> Fix For: 4.0.0, 3.2.0
>
> Attachments: HIVE-23033.1.patch, HIVE-23033.2.branch-3.patch,
> HIVE-23033.2.patch
>
>
> * The inital value for this table in the schema scripts was removed in
> HIVE-17566:
> https://github.com/apache/hive/commit/32b7abac961ca3879d23b074357f211fc7c49131#diff-3d1a4bae0d5d53c8e4ea79951ebf5eceL598
> * This was fixed in a number of scripts in HIVE-18781, but not for mssql:
> https://github.com/apache/hive/commit/59483bca262880d3e7ef1b873d3c21176e9294cb#diff-4f43efd5a45cc362cb138287d90dbf82
> * This is as is since then
> When using the schematool, the table gets initialized by other means.
> This could be backported to all active branches for 3.x as well.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
