[
https://issues.apache.org/jira/browse/TINKERPOP-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Margitus updated TINKERPOP-1587:
----------------------------------------
Description:
The subgraph traversal step does not respect the cardinality of properties when
executed on a graph remotely accessed from Gremlin Server. When queried, only
one value of a multi-value property is returned. The following Java-based
traversal illustrates the issue on The Crew graph. Below g is a Graph
Traversal Source created using the withRemote() method on the EmptyGraph.
{code}
GraphTraversal<Edge, Object> traversal
=g.E().hasLabel("develops").subgraph("subgraph").cap("subgraph");
TinkerGraph subgraph = (TinkerGraph)traversal.next();
GraphTraversalSource sg = subgraph.traversal();
GraphTraversal<Vertex, Object> locationTraversal = sg.V(1L).values("location");
while (locationTraversal.hasNext()) {
System.out.println(locationTraversal.next());
}
{code}
This traversal should return four locations {code} {id=1, name=[marko],
location=[san diego, santa cruz, brussels, santa fe], label=person} {code}
however it only returns santa fe.
was:The subgraph traversal step does not respect cardinality of properties
when executed on a graph remotely accessed from Gremlin Server, and only
returns one value of a multi-value property. This was discovered on a custom
graph, and then confirmed using The Crew graph. The following Java-based
traversal illustrates the issue:
> Gremlin Server Subgraph Cardinality Not Respected
> -------------------------------------------------
>
> Key: TINKERPOP-1587
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1587
> Project: TinkerPop
> Issue Type: Bug
> Components: io
> Affects Versions: 3.2.3
> Reporter: Michael Margitus
> Assignee: stephen mallette
>
> The subgraph traversal step does not respect the cardinality of properties
> when executed on a graph remotely accessed from Gremlin Server. When
> queried, only one value of a multi-value property is returned. The following
> Java-based traversal illustrates the issue on The Crew graph. Below g is a
> Graph Traversal Source created using the withRemote() method on the
> EmptyGraph.
> {code}
> GraphTraversal<Edge, Object> traversal
> =g.E().hasLabel("develops").subgraph("subgraph").cap("subgraph");
> TinkerGraph subgraph = (TinkerGraph)traversal.next();
> GraphTraversalSource sg = subgraph.traversal();
> GraphTraversal<Vertex, Object> locationTraversal =
> sg.V(1L).values("location");
> while (locationTraversal.hasNext()) {
> System.out.println(locationTraversal.next());
> }
> {code}
> This traversal should return four locations {code} {id=1, name=[marko],
> location=[san diego, santa cruz, brussels, santa fe], label=person} {code}
> however it only returns santa fe.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
