[
https://issues.apache.org/jira/browse/TINKERPOP-1280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262536#comment-15262536
]
Daniel Kuppitz commented on TINKERPOP-1280:
-------------------------------------------
Having this default method in the {{VertexProgram}} interface would be an easy
non-breaking solution, no?
{code}
public default Set<TraverserRequirement> getTraverserRequirements() {
return Collections.emptySet();
}
{code}
> VertexPrograms should declare traverser requirements
> ----------------------------------------------------
>
> Key: TINKERPOP-1280
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1280
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.0-incubating
> Reporter: Daniel Kuppitz
>
> VertexPrograms should declare their {{TraverserRequirement}} which can then
> be propagated by the {{program()}} step. Most VPs (at least the ones I have
> written so far) rely on (labeled) path information and thus will fail if the
> actual traversal doesn't use any other steps with the same traverser
> requirements. I keep running into this issue whenever I write a new VP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
