[
https://issues.apache.org/jira/browse/TINKERPOP-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16533723#comment-16533723
]
Horacio Hoyos Rodriguez edited comment on TINKERPOP-1998 at 7/5/18 2:29 PM:
----------------------------------------------------------------------------
Further findings:
On test GraphTest.shouldRemoveEdges, we have:
bq.
final Vertex a = vertices.get(random.nextInt(vertices.size()));
final Vertex b = vertices.get(random.nextInt(vertices.size()));
if (a != b) {
edges.add(a.addEdge(graphProvider.convertLabel("a" + UUID.randomUUID()),
b));
created = true;
}
Which means labels for edges are random UUIDs. If this is the case, then what
is the correct use of edge labels? I assumed that the edge label defined a
logical grouping of edges, and hence I have a separate table/collection for
each possible type of edge. But if labels are just properties, and as such I
only require a single "edge" table/collection. Note that having a single
collection for ALL edge labels makes neighbour traversal much slower (search
one collection with ALL edges, vs a smaller collection with edges of a specific
type).
was (Author: arcanefoam):
Further findings:
On test GraphTest.shouldRemoveEdges, we have:
{{
final Vertex a = vertices.get(random.nextInt(vertices.size()));
final Vertex b = vertices.get(random.nextInt(vertices.size()));
if (a != b) {
edges.add(a.addEdge(graphProvider.convertLabel("a" + UUID.randomUUID()),
b));
created = true;
}
}}
Which means labels for edges are random UUIDs. If this is the case, then what
is the correct use of edge labels? I assumed that the edge label defined a
logical grouping of edges, and hence I have a separate table/collection for
each possible type of edge. But if labels are just properties, and as such I
only require a single "edge" table/collection. Note that having a single
collection for ALL edge labels makes neighbour traversal much slower (search
one collection with ALL edges, vs a smaller collection with edges of a specific
type).
> IoGraphTest use different schemas for standard and readGraph configurations
> ---------------------------------------------------------------------------
>
> Key: TINKERPOP-1998
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1998
> Project: TinkerPop
> Issue Type: Improvement
> Affects Versions: 3.3.0
> Reporter: Horacio Hoyos Rodriguez
> Priority: Minor
>
> In ArangoDB labels used by vertices and edges must be known in order to
> create a graph. As a result this information should be available at startup,
> i.e via configuration. For example _shouldReadWriteModernToFileWithHelpers_
> test expects a different schema from the *standard* graph than from the
> *readGraph*, the latter attempts to create vertices in a (default) vertex
> collection instead of using the people or software ones that were used for
> the former.
> It would also help, for graph technologies that require schemas, to have a
> document that describe the schemas used/expected in the tests. I am
> collecting this information atm, but having to run failing tests to capture
> what label/edges I am missing for each test is a PITA.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
