#Arangodb client code
On my work computer, the same code was used to create the graph and populate it with the same data, but there no errors were raised. More informationĪ last piece of information is that I'm running this on my personal laptop when the error is raised. However, without the the ttl-parameter, the AQL approach gives the same error as using journals.all(). When I replace the journals.all() with AQL, and increase the TTL parameter, it works without errors: for journal in db.aql.execute("FOR j IN journals RETURN j", ttl=3600): if I do print(len(journals.all()) it outputs "1361" with no errors. If I iterate over the entire collection fast, i.e. Insights to the causeįrom ArangoDB Cursor Timeout, and from this issue, I suspect that it's because the cursor's TTL has expired in the database, and in the python stacktrace something like this is seen: # Part of the stacktrace in the error: Will be raised when a cursor is requested via its id but a cursor with that id cannot be found.
The problem is that it raises a CursorNextError, and returns HTTP 404 and ERR 1600 from the database, which is the ERROR_CURSOR_NOT_FOUND error: However: this is more than 1000, which is the batch size in the Web Interface - but I don't know if this is of relevance. I have a relatively small dataset, and the journals-collection has only ca. I use python-arango and the code is something like: for journal in journals.all(): journals, and use it to create edges, author, from a person to the given journal. I iterate over an entire vertex collection, e.g.
0 kommentar(er)
