[
https://issues.apache.org/jira/browse/TINKERPOP-1130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
stephen mallette updated TINKERPOP-1130:
----------------------------------------
Labels: breaking (was: )
This institutes a breaking change as there are many inconsistencies in testing
gryo compatibilty. To ensure these inconsistencies don't proceed past 3.3.0,
the {{RequestMessage}} and {{ResponseMessage}} altered their binary formatting
slightly which could lead to serialization problems between 3.2.x and 3.3.x.
Note that the Gremlin Server protocol itself hasn't changed, but that these
classes are now simply registered with the {{GryoMapper}} itself in the
TinkerPop range of ids and not in the user (i.e. custom range of ids).
> 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: Improvement
> Components: io, test-suite
> Affects Versions: 3.1.1-incubating
> Reporter: Marko A. Rodriguez
> Labels: breaking
>
> 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)
