[tinkerpop] 01/03: Added some caveats for pagination in the recpies CTR

[sp...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

spmallette pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/tinkerpop.git

commit ccae83433b11a57cfb414d8161a0360f9df281ff
Author: Stephen Mallette <sp...@genoprime.com>
AuthorDate: Thu Oct 11 08:09:10 2018 -0400

    Added some caveats for pagination in the recpies CTR
---
 docs/src/recipes/pagination.asciidoc | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/src/recipes/pagination.asciidoc b/docs/src/recipes/pagination.asciidoc
index 7e7da8d..63393d4 100644
--- a/docs/src/recipes/pagination.asciidoc
+++ b/docs/src/recipes/pagination.asciidoc
@@ -76,3 +76,13 @@ t = g.V().hasLabel('person');[]
 t.next(2)
 t.next(2)
 ----
+
+A further consideration relates to the order in which results are returned. TinkerPop does not guarantee that the
+order of the items returned on the same traversal will be the same order each time the traversal is iterated.
+TinkerPop only guarantees that it does not re-shuffle the order provided by the underlying graph database. This
+guarantee has two implications:
+
+1. Iteration order is dependent on the underlying graph database. Some graphs may guarantee ordering and some may not
+and still some others may guarantee ordering but only under certain conditions. Consult the documentation of the
+graph database for more information on this.
+2. Use `order()`-step to make iteration order explicit if guarantees are required.