Github user mpollmeier commented on the issue:
https://github.com/apache/tinkerpop/pull/705
That's very true. I just experimented with deep clones and it doesn't look
straightforward
* kryo can do it directly, but all referenced classes need a
no-arg-constructor, and since there a
Github user robertdale commented on the issue:
https://github.com/apache/tinkerpop/pull/705
This doesn't look like a deep copy e.g. modifying a property would be
reflected in both graphs. Which may be fine. I think any limitations should be
noted in the clone method comment.
---
GitHub user mpollmeier opened a pull request:
https://github.com/apache/tinkerpop/pull/705
make TinkerGraph cloneable
most people use tinkergraph for testing, and if there are traversals that
manipulate the graph, it's useful to be able to clone it up front, especially
for larger g
