[ https://issues.apache.org/jira/browse/TINKERPOP-1415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15436848#comment-15436848 ]
Bryn Cooke commented on TINKERPOP-1415: --------------------------------------- Closed, but just want to throw in the idea that PathRetractionStrategy could pick up the specific variables that are required rather than globally disabling path retraction. > Vertex programs that rely on getting path parameters can't work > --------------------------------------------------------------- > > Key: TINKERPOP-1415 > URL: https://issues.apache.org/jira/browse/TINKERPOP-1415 > Project: TinkerPop > Issue Type: Bug > Components: process > Affects Versions: 3.2.1 > Reporter: Bryn Cooke > > Recently some of our vertex programs have started failing. > They rely of being able to retrieve an element out of the path. > However, whereas this used to work now the path element isn't there anymore. > The root cause is that path retraction doesn't know that the vertex program > is interested in the path and therefore culls out parameter. > I can understand why it does this, but there seems to be no way of exposing > the vertex program path requirements such that PathRetractionStrategy can > pick them up and do the right thing. > I tried hacking together a solution by making ProgramVertexProgramStep > implement Scoping. This did fix the issue, but I am not confident that this > is the way to go. -- This message was sent by Atlassian JIRA (v6.3.4#6332)