Cosoms Graph DB Vertex specification: outE missing

[mattKorwel]

https://docs.microsoft.com/en-us/azure/cosmos-db/graph/gremlin-support#gremlin-wire-format states that

outE | This property contains a list of out edges from a vertex. Storing the adjacency information with vertex allows for fast execution of traversals. Edges are grouped based on their labels.

outE will be present on the vertex object. it is however not present. using the data from the .net quickstart i see a vertex with edges, but the edges are not returned. is there a flag to pass, if so this should be documented. is this a bug/

if this is a bug, it is a critical issue as easily referencing a vertices out edges is critical for fast query performance.

thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 0374b015-1139-9df8-6c96-a8657a088748
• Version Independent ID: 2e18d44d-de3c-eee5-7932-0a5a967e9b17
• Content: Azure Cosmos DB Gremlin support and compatibility with TinkerPop features
• Content Source: articles/cosmos-db/graph/gremlin-support.md
• Service: cosmos-db
• Sub-service: cosmosdb-graph
• GitHub Login: @manishmsfte
• Microsoft Alias: mansha

[MayankBargali-MSFT]

@mattKorwel Thank you for your feedback! We will review and update as appropriate.

[KalyanChanumolu-MSFT]

@mattKorwel Thank you for the detailed feedback. This is being assigned to the content author to evaluate and update the documentation as appropriate.

[SnehaGunda]

@mattKorwel you would use the has filter like this: g.V().has('firstName', 'Thomas').outE()

[mattKorwel]

hi @SnehaGunda, yes i can use the oute step, but that's not what the docs say the behavior is. if that is not the behavior, the outV being stored on the document, the docs should change.

as an end user, being able to get the vertex is cheaper and quicker than the vertex and out steps.

[manishmsfte]

OutE is a separate step which needs to be performed to get the list of edges. If the intent is just to get the Vertex, you can use g.V() but if it is needed to get to the edges then it is needed to be explicitly used the step g.V().OutE()

"outE | This property contains a list of out edges from a vertex."

• This statement is in the context of step outE, if you specify then you get.....

"Storing the adjacency information with vertex allows for fast execution of traversals."

• This statement highlights an optimization point that if you specify the adjacency information then you don't need to use outE / traversal which makes your query cheaper.

Edges are grouped based on their labels.

• This is pretty standard in LPG type graphs.

Hope this helps.

[manishmsfte]

please-close