Allow a subgraph to be attached to an existing graph

[aschrijver]

See the discussion on this thread in the Vert.x google group: https://groups.google.com/d/msg/vertx/eIjzdQI23ss/hjYUtJcxVKcJ

[ramukima]

Not sure if you have done something related to this. Are you planning on keeping this module active and make a stable version out of it ?

[aschrijver]

Hi,

Although I have limited time to spend on it, I do intend to keep the module active. I did not do any work on attaching subgraphs yet.

Considerations that make me hesitant to extend the current version much further is the fact that Tinkerpop3 is in the works and constitutes a major rewrite of much of the funcitonality.
Also I tried to implement transaction support that spans multiple actions, but without success as it would require implementations of ThreadedTransactionalGraph in the Tinkerpop implementations (which isn't implemented in most graphdb's).
This 'attaching subgraphs' feature as well as broader transaction support make me reconsider whether I should base the persistor on Blueprints, or whether it is better to make it interface to a Rexster server instead.

Having said that...this issue is marked as an enhancement. Given the current feature set that is described in the readme, which of the features do you currently perceive as unstable (or even buggy)?

[ramukima]

I am aware of the changes going into TinkerPop3. The core APIs are changing but not to an extent you would get concerned too much about it. Obviously, changes to Gremlin, Frames, Rexter, Pipes are much bigger.

Gremlin takes most of what Rexter used to provide so a Gremlin server. In any case, your module is useful.

It may happen in future for your module that it becomes a passthrough to talking to a Gremlin server over the wire, but I can not see that your module will be useless.

[aschrijver]

Thank you! See also my comments to #12