1. Docs
2. Reference
3. REST API Docs
4. Schema
5. GraphSchemaLimits

Engine limits applied to every graph query. A selector limit is checked before the query runs: a selector that exceeds it is rejected. A result limit clips the answer and sets meta.resultMode to ’truncated'.

Properties

• maxDepth integer required
  Maximum traversal depth per step. A selector limit: a step whose depth.max exceeds it is rejected.
• maxTraverseSteps integer required
  Maximum number of traversal steps per query. A selector limit: a query with more steps is rejected.
• maxScopeAccounts integer required
  Maximum number of cloud accounts scope.accounts may list. A selector limit: a longer list is rejected.
• maxScopeStacks integer required
  Maximum number of stacks scope.stacks may list. A selector limit: a longer list is rejected.
• maxGroupByFields integer required
  Maximum number of fields aggregate.groupBy may name. A selector limit: naming more is rejected.
• maxAnchorNodes integer required
  Maximum number of anchor nodes one query resolves, and the upper bound on anchor.limit. When more nodes match, the result is clipped and reported as truncated - except under a selector that also traverses, where an engine-imposed clip is rejected instead. Also a selector limit: a match.fields[…].in list longer than this is rejected.
• maxFanout integer required
  Maximum new nodes discovered per traversal level. A result limit.
• maxNodes integer required
  Maximum total nodes held by one query evaluation. A result limit.
• maxPaths integer required
  Maximum evidence paths returned. A result limit.
• maxRecordedCrossings integer required
  Maximum number of edge crossings a traversal step records while walking. A result that reaches this bound is returned with resultMode ’truncated’ rather than rejected.
• maxPageSize integer required
  Maximum page size. Applied silently rather than as a rejection or a truncation: a page.pageSize above this value is reduced to it.