Allow cross-version copy in neo4j-admin copy
The copy command can be used to clean up inconsistencies, compact stores, and do an upgrade at the same time. Also, we can allow a bigger range of upgrades, e.g. 3.4 directly to 4.1, skipping the intermediate steps of 3.5.latest -> 4.0.latest -> 4.1. Those steps are needed to migrate the schema, but since we don't copy the schema store at all during a copy, they are not needed. The schema will have to be re-created in the end on the copied to database.
Showing
+157 -44
Please register or sign in to comment