[
https://issues.apache.org/jira/browse/TINKERPOP3-892?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14959938#comment-14959938
]
Matt Frantz commented on TINKERPOP3-892:
----------------------------------------
Forum topic referenced above:
https://groups.google.com/forum/#!topic/gremlin-users/y43a6LXL1mk
> Saving Graph to file won't save graph variables
> -----------------------------------------------
>
> Key: TINKERPOP3-892
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-892
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.0.1-incubating
> Reporter: Flavio Cordova
> Assignee: Marko A. Rodriguez
> Priority: Critical
>
> When you save a graph using writeGraph graph variables are not saved along
> with all the vertices and edges, so you can't fully recover the graph when
> you read the file.
> In the forum there's a thread called "Saving graph variables to File" that
> will discuss the matter in details but basically "I understand the API should
> handle variables and persist then properly, probably adapting it as a vertex
> to be compliant to the format, but it should be transparent to the developer,
> something like neo4J does for multi-properties. IF the way they are written
> to the file were not good enough [for me] then I could be able to change it
> writting a custom writer/reader, but not the way around."
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
