CODEWITHSUNDEEP
arangodb
augustin-s
augustin-s

Reputation: 683

arangodb AQL Limit > 1000

I observe a problem when using LIMIT > 1000 in AQL:

Here are the examples:

FOR e IN subcategoryOf
LIMIT 1000
RETURN { "id": e._id, "text": e.text }
--> Fast, below a second


FOR e IN subcategoryOf
LIMIT 1, 1000
RETURN { "id": e._id, "text": e.text }
--> Fast, below a second


FOR e IN subcategoryOf
LIMIT 1, 1001
RETURN { "id": e._id, "text": e.text }
--> not answering after 20 seconds, manually aborted then.

Does anybody observe the same or have a hint for me?

I'm using ArangoDB 2.3.0 on Windows, and the aardvark AQL editor.

Upvotes: 3

Views: 1153

Answers (1)

stj
stj

Reputation: 9097

Thanks, this was a bug in the web interface. I have fixed it in this commit: https://github.com/triAGENS/ArangoDB/commit/7656efd82fcbb31160d2ca4842f72190491101b8

Upvotes: 8

Related Questions