Upgrading and skipping versions.

[Gary Gendel]

We're deploying ArangoDB as part of a service at the customer's location.  The problem we've been running into is that some of our larger customers are reticent to upgrade software while a project is in active development.  This means that we might have to wait years to upgrade ArangoDB to a newer version.  This means that may be several versions behind.

Our strategy is to use arangodump and arangorestore when upgrading AranogDB.  Early in the 3.1 or 3.2 version upgrades we had an issue where the arangorestore failed because we had renamed collections (the pmlibtype collection became pmlibspec and the pmvartype collection became pmlibtype) that caused a collection index name problem.  We had to edit the arangodump to fix it.  We've not run into any other issues since then.

Can I rely on arangodump and arangorestore to be used to upgrade across a jump of several versions?  I would assume so, but I want confirmation so we can breathe easier when dealing with our customers.