-
Notifications
You must be signed in to change notification settings - Fork 116
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
Request to Upgrade OrientDB to Version 3.2.36 #1641
Comments
Hello, Thank you for reaching out and for testing Mesh with OrientDB 3.2.36. We want to inform you that we are now providing Mesh SQL as an open-source solution, using the MariaDB connector. With this shift, we are no longer planning updates for OrientDB. However, if a commercial request is made, we can evaluate an update as part of a dedicated project. Let us know if you have any further questions. |
Hello @philippdoerre thanks, Where can i find doc about Mesh SQL integration with an existing mesh instance running in 2.X ? |
@cschockaert : https://www.gentics.com/mesh/docs/administration-guide/ |
Hello @philippdoerre, yes we are studying the migration to latest mesh with sql connector because we got a lot of problem with orientdb. |
@cschockaert we can use your backup for doing the migration! can you please provide the current size of the dump? |
Hello @philippdoerre sry for delay our db size is around 500 MBytes (zipped) |
@cschockaert our offer is prepared - can you please send me your official contacts via email, so i can send the offer? [email protected] - thanks |
Yes doin that tanks @philippdoerre |
Hello,
Would you consider upgrading Mesh to use the latest OrientDB version 3.2.36?
I encountered a bug that has been fixed by the OrientDB team in this version. I successfully tested Mesh 2.1.10 with OrientDB 3.2.36, and it works without issues.
I believe the upgrade should be straightforward — updating the BOM POM file and running the full suite of JUnit tests should be sufficient.
Thank you!
The text was updated successfully, but these errors were encountered: