[jira] [Commented] (HIVE-26112) Missing scripts for metastore

["Abhay (Jira)" <ji...@apache.org>]

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

Abhay commented on HIVE-26112:
------------------------------

@[~asolimando], Just trying to understand a bit more about the ticket here.
{noformat}
If the versions don't match between metastore (the sysdb one) and HMS, how can we easily keep the two in sync and make sure nothing slips through the cracks?{noformat}
I was of the opinion that *upgrade.order.hive* and *upgrade.order.derby/upgrade.order.mysql etc.* can have different contents since some features might change only the sysdb/information_schema table/views or vice versa. Just trying to understand why is it important to keep them in sync?



@pvary your earlier comment also seemed to suggest the same. Thank you

 

 

> Missing scripts for metastore
> -----------------------------
>
>                 Key: HIVE-26112
>                 URL: https://issues.apache.org/jira/browse/HIVE-26112
>             Project: Hive
>          Issue Type: Bug
>          Components: Metastore
>    Affects Versions: 4.0.0-alpha-2
>            Reporter: Alessandro Solimando
>            Assignee: Alessandro Solimando
>            Priority: Blocker
>             Fix For: 4.0.0-alpha-2
>
>
> The version of the scripts for _metastore_ and _standalone-metastore_ should be in sync, but at the moment for the metastore side we are missing 3.2.0 scripts (in _metastore/scripts/upgrade/hive_), while they are present in the standalone_metastore counterpart(s):
> * hive-schema-3.2.0.*.sql
> * upgrade-3.1.0-to-3.2.0.*.sql
> * upgrade-3.2.0-to-4.0.0-alpha-1.*.sql
> * upgrade-4.0.0-alpha-1-to-4.0.0-alpha-2.*.sql



--
This message was sent by Atlassian Jira
(v8.20.7#820007)