Skip to content

Conversation

@anvie
Copy link

@anvie anvie commented Dec 18, 2013

configurable via "faunus.graphson.mode"

Tested and worked for upgrading data from Titan 0.3.x to 0.4.x
using GraphSON extended via Faunus 0.3.x to generate output using "g._()"
and use Faunus 0.4.x to process the graphson generated by 0.3.x as the input.

configurable via "faunus.graphson.mode"

Tested and worked for upgrading data from Titan 0.3.x to 0.4.x
using GraphSON extended via Faunus 0.3.x to generate output using "g._()"
and use Faunus 0.4.x to process the graphson generated by 0.3.x as the input.
(cherry picked from commit 8d2241f)
@okram
Copy link
Contributor

okram commented Dec 18, 2013

Thank you for your contribution. With Titan 0.5.0 we will be providing a binary format that fully supports Titan upgrading into the future -- supports multi-properties, unidirected edges, and arbitrary serializers beyond just the primitives of JSON.

I super appreciate your effort and I think we will be able to get some of this work (for the sake of people wanting to use GraphJSON) into Titan 0.5.0. Please keep this work around and when the 0.5.0 branch comes out, lets discuss about merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants