DOC-142/traversal-projections

3.10/aql/graphs-traversals.md

@@ -134,8 +134,10 @@ FOR vertex[, edge[, path]]
  case when a nested traversal is fed with several tens of thousands of start
  vertices, which can then be distributed randomly to worker threads for parallel
  execution.
-
  {% include hint-ee.md feature="Traversal parallelization" plural=false %}
+ - **maxProjections** (number, *optional*): Specifies the number of document
+ attributes per FOR loop to be used as projections. The default value is `5`.
+ {% include hint-ee.md feature="Traversal projections" plural=true %}
  - **weightAttribute** (string, *optional*): Specifies the name of an attribute
  that is used to look up the weight of an edge. If no attribute is specified
  or if it is not present in the edge document then the `defaultWeight` is used.

3.10/aql/operations-for.md

@@ -196,6 +196,11 @@ there are a few corner cases where it can make sense:
  projections, if the cost of projections is higher than doing copies of the
  full documents. This can be the case for very small documents.
 
+{% hint 'info' %}
+Starting with version 3.10, `maxProjections` can be used in 
+[Graph Traversals](graphs-traversals.html#working-with-named-graphs) (Enterprise Edition only).
+{% endhint %}
+
 ### `useCache`
 
 <small>Introduced in: v3.10.0</small>

3.10/release-notes-new-features310.md

@@ -109,6 +109,16 @@ geo indexes need to be dropped and recreated after an upgrade.
 See [Legacy Polygons](indexing-geo.html#legacy-polygons) for
 details and for hints about upgrading to version 3.10 or later.
 
+### Traversal Projections (Enterprise Edition)
+
+Starting with version 3.10, you can use projections in graph traversals to
+follow edges connected to a start vertex, up to a variable depth.
+
+The `maxProjections` is now introduced as an option when
+[working with named graphs](aql/graphs-traversals.html#working-with-named-graphs).
+
+See also [how to use `maxProjections` with FOR loops](aql/operations-for.html#maxprojections).
+
 ### Number of filtered documents in profiling output
 
 The AQL query profiling output now shows the number of filtered inputs for each execution node