[
https://issues.apache.org/jira/browse/HIVE-25707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17469482#comment-17469482
]
Rahul Pathak commented on HIVE-25707:
-------------------------------------
This is also useful if SchemaTool upgrade fails for some data inconsistency,
like duplicate records in tables NEXT_**_ID
Rerunning SchemaTool upgrade in such case create more issues. There should be
way to put back the state as it was before starting the upgrade steps
> SchemaTool may leave the metastore in-between upgrade steps
> -----------------------------------------------------------
>
> Key: HIVE-25707
> URL: https://issues.apache.org/jira/browse/HIVE-25707
> Project: Hive
> Issue Type: Bug
> Reporter: Zoltan Haindrich
> Priority: Major
>
> it seems like:
> * schematool runs the sql files via beeline
> * autocommit is turned on
> * pressing ctrl+c or killing the process will result in an invalid schema
> https://github.com/apache/hive/blob/6e02f6164385a370ee8014c795bee1fa423d7937/beeline/src/java/org/apache/hive/beeline/schematool/HiveSchemaTool.java#L79
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
