You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2016/02/05 18:35:39 UTC

[jira] [Created] (TINKERPOP-1130) Each release should store Kryo/GraphSON/GraphML versions to ensure future compatibility

Marko A. Rodriguez created TINKERPOP-1130:
---------------------------------------------

             Summary: Each release should store Kryo/GraphSON/GraphML versions to ensure future compatibility
                 Key: TINKERPOP-1130
                 URL: https://issues.apache.org/jira/browse/TINKERPOP-1130
             Project: TinkerPop
          Issue Type: Test
          Components: io, test-suite
    Affects Versions: 3.1.1-incubating
            Reporter: Marko A. Rodriguez


I think we should make a new toy data set that has all the graph structure features in it -- vertices, edges, vertex properties, multi-properties, meta-properties, graph variables, different edge labels with different property keys, etc. etc.

The graph doesn't have to be big, it just needs to cover all the features. Next, we should then stamp out a version of that file at every release:

{code}
graph-test-x.y.z.xml
graph-test-x.y.z.kryo
graph-test-x.y.z.json
graph-test-x.y.z-typed.json
{code}

Then we should have a test case that verifies that the current SNAPSHOT {{GryoReader}}, {{GraphSONReader}}, {{GraphMLReader}}, etc. can still read those files. If they can't, then we have introduced a change in our serialization format.





--
This message was sent by Atlassian JIRA
(v6.3.4#6332)