Migration of lightWeightVersionStore to versionStore2

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

tim-erwin

Hello,

our application heavily depends on the version store. Users can freeze states of documents - technically creating versions of which the uuids are stored in our db.

However, during the upgrade from 2.9 to 3.0 not only the store format changed, but also the uuids of the migrated nodes. That basically destroys our data, all the links to versions are broken. Is that a case that is so uncommon? I haven't found anything about it in the forums. Is there a way to properly migrate the version store?

Regards,
Tim

tim-erwin

Hello again,

something even worse happens during the upgrade process: versions get deleted!

I set up a fresh alfresco, added 3 simple text files, made them versionable, made some versions (changing the content each time). Then I took the whole data over to alfresco 3.0, the migration finished without any errors in the log, however, only the last version of each item still exists - which is quite pointless, as they are equal to their corresponding current element, anyways.

I would consider both behaviors (this one and previous post) serious bugs. I have to trust alfresco, that I can preserve our data somehow and use it in recent versions. We are stuck to 2.9 for now.

Cheers,
Tim