Hey Simran, Too bad for the RID equivalent, hopefully, we will manage,
Interesting alternatives, using a sorted index with the timestamp is a really cool idea (a bit expensive but sometimes i guess you have to make choices) I understand what you're proposing with the cursor and i'd be very happy to be satisfied with those, now what bothers me is that (as it seems to me when i check out your documentation) with the java driver once a cursor is created i must consumes all of its content in one pass. I mean, not in one pass where i absorb everything at once in a single chunk and make everything crash because i don't have enough memory, 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). So, in that aspect it doesn't exactly meet our needs, i'm still curious though, is it only a limitation from the java driver ? Because when i read the documentation of the HTTP API it seems like a cursor indeed stays alive, so maybe we could have some workaround about this. 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 Thank you again for your time and answers, it's very valuable to us :) Best Regards, Cyprien -- 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.
