[jira] [Closed] (TINKERPOP-1727) Bytecode object shallow copied when traversals are cloned
[ https://issues.apache.org/jira/browse/TINKERPOP-1727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ted Wilmes closed TINKERPOP-1727. - Resolution: Fixed Fix Version/s: 3.2.6 3.3.0 > Bytecode object shallow copied when traversals are cloned > - > > Key: TINKERPOP-1727 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1727 > Project: TinkerPop > Issue Type: Bug > Components: process >Affects Versions: 3.3.0, 3.2.5 >Reporter: Ted Wilmes >Assignee: Ted Wilmes > Fix For: 3.3.0, 3.2.6 > > > The {{bytecode}} member of traversal objects are only shallow copied when a > traversal is cloned. This causes issues because any updates to the clone will > be propagated to cloned traversal. > {code} > gremlin> g = TinkerGraph.open().traversal() > ==>graphtraversalsource[tinkergraph[vertices:0 edges:0], standard] > gremlin> traversal = g.V().out();null > ==>null > gremlin> clonedTraversal = traversal.asAdmin().clone();null > ==>null > gremlin> clonedTraversal.out().out();null > ==>null > gremlin> traversal.getBytecode() > ==>[[], [V(), out(), out(), out()]] > gremlin> clonedTraversal.getBytecode() > ==>[[], [V(), out(), out(), out()]] > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[GitHub] tinkerpop pull request #676: TINKERPOP-1727: Bytecode object shallow copied ...
Github user asfgit closed the pull request at: https://github.com/apache/tinkerpop/pull/676 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. ---
[jira] [Commented] (TINKERPOP-1716) Traversal strategies are not applied with remote in Gremlin Console
[ https://issues.apache.org/jira/browse/TINKERPOP-1716?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16092956#comment-16092956 ] stephen mallette commented on TINKERPOP-1716: - The problems with this is related to TINKERPOP-1679 - I'm going to opt out the three failing tests so that we can get a PR up. > Traversal strategies are not applied with remote in Gremlin Console > --- > > Key: TINKERPOP-1716 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1716 > Project: TinkerPop > Issue Type: Bug > Components: server >Affects Versions: 3.2.3, 3.2.5 >Reporter: Jason Plurad > > Originally from a [StackOverflow > post|https://stackoverflow.com/questions/44907843/can-strategies-be-used-with-remote-traversal-in-gremlin]: > This subgraph strategy works (only the `battled` edges are returned) with a > remote from Gremlin-Python: > {noformat} > from gremlin_python import statics > from gremlin_python.structure.graph import Graph > from gremlin_python.process.graph_traversal import __ > from gremlin_python.process.strategies import * > from gremlin_python.driver.driver_remote_connection import > DriverRemoteConnection > statics.load_statics(globals()) > graph = Graph() > g = > graph.traversal().withRemote(DriverRemoteConnection('ws://localhost:8182/gremlin','g')).withStrategies(SubgraphStrategy(edges=__.hasLabel('battled'))) > g.E().label().groupCount().toList() > {noformat} > But the subgraph strategy does not work (all edges are returned) with a > remote from the Gremlin Console: > {noformat} > graph = EmptyGraph.instance() > g = > graph.traversal().withRemote('conf/remote-graph.properties').withStrategies(SubgraphStrategy.build().edges(__.hasLabel("battled")).create()) > g.E().label().groupCount().toList() > {noformat} -- This message was sent by Atlassian JIRA (v6.4.14#64029)