dengzhhu653 commented on PR #4744:
URL: https://github.com/apache/hive/pull/4744#issuecomment-1877100134
@zhangbutao
> But i think it should not be a problem, users should know that if they
upgraded the metadata schema, they also should upgrade the HMS binary package
at the same.
In my opinion, the upgrade for schema and the binary can't happen at the
same time, especially if there are multiple different HMS instances and
clusters. For this change, we drop columns from the old table, for safety we
need to back up the table first before doing any operation, and avoid the old
HMS writing into this table during the upgrade, you cannot tell the user not
roll back to the old version if they find something wrong.
> Maybe any change on metadata schema can make old HMS occur error, not
just this PR.
that's possible, so we need to reduce the possibility of such thing
recurring, especially for the user to recover from failure
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
