Describe the bug
This is relevant when using a proxy store to connect gafferpop to an existing a graph, the gremlin functions will fail. This is due to a slight implementation oversight where the gafferpop element generators are included in the operation chains that are used. This is an issue when using the proxy store as the whole chain is sent to the remote graph which may not have tinkerpop library and serialisation is currently missing.
Expected behaviour
A better solution would be to have this element translation happen locally instead. Essentially only the 'plain' Gaffer operations should be executed on the graph via gafferpop, all gafferpop specific bits should happen before or on the results outside of the chain sent to the remote graph.
Describe the bug This is relevant when using a proxy store to connect gafferpop to an existing a graph, the gremlin functions will fail. This is due to a slight implementation oversight where the gafferpop element generators are included in the operation chains that are used. This is an issue when using the proxy store as the whole chain is sent to the remote graph which may not have tinkerpop library and serialisation is currently missing.
Expected behaviour A better solution would be to have this element translation happen locally instead. Essentially only the 'plain' Gaffer operations should be executed on the graph via gafferpop, all gafferpop specific bits should happen before or on the results outside of the chain sent to the remote graph.