> > ... but in one single continuous timelapse. With the appropriate > pagination (the infamous RIDs) we could pause our process and resume it > later on (for whatever reason, crash of the system, connectivity problem > and such). >
Cursors have a TTL, but in the event of a server crash they would be gone regardless of the driver as far as I know. I'm curious how RIDs are implemented; is it possible to resume any kind of query or only queries which basically return documents as-is? ArangoExport could also be an option, we would have to change a bit our > approach and build some kind of workaround since it's not available from > the java driver but this seems feasible > There is some work on the way to exploit the sortedness of the primary index using the RocksDB storage engine: https://github.com/arangodb/arangodb/pull/7788 That in combination with a streaming cursor and a simple FOR doc IN coll RETURN doc query, it might be a possible alternative to arangoexport. -- 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.
