[
https://issues.apache.org/jira/browse/TINKERPOP-1424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15623895#comment-15623895
]
Daniel Kuppitz commented on TINKERPOP-1424:
-------------------------------------------
No, this is not longer an issue. The problem from the description was actually
implemented as a test case in TINKERPOP-1280's PR:
https://github.com/apache/tinkerpop/pull/404/files#diff-1ae539eeb6f0cc23749ee7b6c4bee881R2351
> PathRetractionStrategy can easily break VertexPrograms
> ------------------------------------------------------
>
> Key: TINKERPOP-1424
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1424
> Project: TinkerPop
> Issue Type: Bug
> Components: process
> Affects Versions: 3.2.1
> Reporter: Daniel Kuppitz
>
> I just ran into an issue where I had to remove {{PathRetractionStrategy}}
> from the traversal strategies. The traversal was something like this:
> {code}
> g.V().out().as("a").out().program(myVertexProgram)
> {code}
> ..and {{myVertexProgram}} tried to access the path label "a". This doesn't
> work if {{PathRetractionStrategy}} is used.
> I think we need to extend VertexPrograms, like in TINKERPOP-1280. If a
> VertexProgram has a {{LABELED_PATH}} requirement, it should also provide
> information about which labels it needs access to.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
