Skip to content
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

[Other]: Data Migration from v3.4.0 to v3.8.0 Post-MySQL Deprecation #2554

Closed
zhaolibo1989 opened this issue Aug 26, 2024 · 4 comments
Closed
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@zhaolibo1989
Copy link
Contributor

What would you like to share?

I am currently merging the second development branch based on version v3.4.0 with version v3.8.0. Upon reviewing the Release Notes, I found that the use of MySQL has been discontinued since version v3.5.0. How can I migrate data from the old version, and is there a corresponding tool available?

Additional information

@OpenIM-Blooming said: "The upgrade to 3.5 will automatically migrate," but how can I achieve this?

@zhaolibo1989 zhaolibo1989 added the other Indicates an issue or PR lacks a `triage/foo` label and requires one. label Aug 26, 2024
@zhaolibo1989
Copy link
Contributor Author

In Android APP development, besides upgrading the openim-sdk-core, what else needs to do?

@FGadvancer
Copy link
Member

To upgrade from version 3.4.0 to 3.8.0, first update your server code from 3.4.0 to 3.5.0. Once the server is started, it will automatically perform the data migration from MySQL to MongoDB. Then, upgrade from 3.5.0 to 3.8.0, which will automatically handle the conversion of the sequence data. Of course, make sure to back up your data beforehand to ensure a safe operation.

@zhaolibo1989
Copy link
Contributor Author

zhaolibo1989 commented Aug 26, 2024

To upgrade from version 3.4.0 to 3.8.0, first update your server code from 3.4.0 to 3.5.0. Once the server is started, it will automatically perform the data migration from MySQL to MongoDB. Then, upgrade from 3.5.0 to 3.8.0, which will automatically handle the conversion of the sequence data. Of course, make sure to back up your data beforehand to ensure a safe operation.

In this way, do I have to merge and publish the code twice?

Is there a way to directly merge the code of 3.8 on that branch, and after publishing and running, automatically complete the data migration?

@zhaolibo1989
Copy link
Contributor Author

I found a tool bin up35 to perform the data migration, it was added in v3.5.0 and then removed in v3.7.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
other Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

3 participants