-
Notifications
You must be signed in to change notification settings - Fork 3.4k
HBASE-28812 Upgrade from 2.6.0 to 3.0.0 crashed #6209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
🎊 +1 overall
This message was automatically generated. |
|
💔 -1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
🎊 +1 overall
This message was automatically generated. |
|
@hanke580 said on jira that the patch worked for him. Then we need a +1 to merge this. |
ndimiduk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need this change on master or just branch-3 ? Have we talked about an upgrade strategy that skips a major version release?
Till now I think we'd better commit to both. Whether we can remove this logic on master depend on what we will do on branch-3 in the future. On the second question, I do not think now we can support skipping a major version when upgrading... |
Signed-off-by: Nick Dimiduk <[email protected]> (cherry picked from commit 7f2bb95)
No description provided.