Yes, its most probably the same issue - same collection ID used in several databases - so another workaround would be to change the collectionids to another uniq value.
And yes, a github issue would be better to track this and give you a mail once a version with a fix becomes available. On Wednesday, April 19, 2017 at 10:18:56 AM UTC+2, Georgios Kafataridis wrote: > > Thanks for the update, I appreciate it. > > Just to clear things up, the same bug somehow affects the issue here > https://groups.google.com/forum/#!topic/arangodb/H1WcP1l2B8U ? > > Is there a git issue to track both? Googlegroups is ok I guess, but not so > transparent. > -- 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.
