When we migrated from 2.0.10 to 2.1.2 we encountered an issue that I
described in the
bug https://github.com/orientechnologies/orientdb/issues/4996 (comment from
AlainBod)
Unfortunately, we only noticed this error case after days of running the
new version.
If we try to downgrade the orientdb binay to 2.0.10 (without touching the
DB), we now have errors such as:
orientdb {db=v6}> select expand(out('MatchesBad')) from #13:14;
Error: com.orientechnologies.orient.core.exception.OStorageException: File
with id 4573508286061477957 does not exist.
With binary 2.0.15, we have a different error:
orientdb {db=v6}> select expand(out('MatchesBad')) from #13:14;
Error:
com.orientechnologies.orient.core.exception.OCommandExecutionException:
Error on execution of command: sql.select expand(out('MatchesBad')) from
#13:14
Error: java.lang.NullPointerException
We did not export/import our DB when upgrading the version of OrientDB as
it is stated in the documentation that "Databases created with release
2.0.x are compatible with 2.1, so you don't have to export/import the
database." (http://orientdb.com/docs/2.1/Release-2.1.0.html).
Trying to export the database in 2.1.2 and importing it in 2.0.x doesn't
work (some errors are raised), so I'm out of idea on how to get my
application running again until the bug is fixed and a release is pushed.
Any idea, hints, advice on your side ??
Thank you in advance,
--
---
You received this message because you are subscribed to the Google Groups
"OrientDB" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
