[
https://issues.apache.org/jira/browse/TINKERPOP-1998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16597405#comment-16597405
]
Horacio Hoyos Rodriguez commented on TINKERPOP-1998:
----------------------------------------------------
Hi,
Finally managed to publish the
[notes|https://medium.com/@arcanefoam/implementing-a-tinkerpop3-oltp-provider-9083cc77d01b].
Sadly the graph schema per test information is too long to post alongside, but
please take a look at
[ArangoDBGraphProvider|https://github.com/arcanefoam/blueprints-arangodb-graph/blob/master/src/test/java/com/arangodb/tinkerpop/gremlin/ArangoDBGraphProvider.java]
to see what are all the different schemas that are needed.
Cheers!
> 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
> Components: test-suite
> 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)
