Hi, you may obtain older packages via: https://www.arangodb.com/repositories/arangodb31/CentOS_6/x86_64/
and install them using the rpm commandline: rpm -Uvh --oldpackage arangodb3-3.1.14-1.x86_64.rpm Cheers, Willi On Monday, April 10, 2017 at 12:56:03 PM UTC+2, Georgios Kafataridis wrote: > > I have arangodb3 3.1.17 (single server: Centos 6.8) and multiple (>50) > databases on the same server. > > We usually clone databases from a source database for each new project, so > all databases share the same initial data and a basic configuration. > We use arangodump and arangorestore to dump and recreate the collections > and import the documents on new databases. > > From v3.1.15 and after, we started noticing some issues with some > documents and collections (which have the exact same _keys and names across > ALL databases). > > Changes in some documents would disappear after a few days (it seems that > they will reset their data to match their original database) or documents > will appear out of thin air in collections. > Updated data in cloned databases are unchanged for several days before > they lose their changes, so I can't monitor when the problem happens. > > In some cases we cloned a finished project (with too many documents) into > a new one (because the content was very similar) and started updating some > documents with new data. After a few days the changed documents in the > cloned project started leaking their data in the original database! > > The problem: documents that have the exact same _key on the exact > collections leak their data in other databases on the same > documents/collections. That never happened until 3.1.15. > > Can I downgrade to a previous version? > -- You received this message because you are subscribed to the Google Groups "ArangoDB" 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.
