[
https://issues.apache.org/jira/browse/TINKERPOP-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235986#comment-16235986
]
Marko A. Rodriguez commented on TINKERPOP-1813:
-----------------------------------------------
The {{SubgraphStep}} itself uses the structure API. That is the nature of the
steps in TinkerPop3. Our semantics assumes the structure API -- plain and
simple. We can not change that. What you want is a direction we are batting
around for TinkerPop4, where we remove the concept of the structure API (or
have a light interface of simple element pointers). If the provider wants to
jump the gun as such, then they can create their own {{SubgraphStep}} and
implement it using nested traversals as they please -- e.g.
{{DseGraphSubgraphStepStrategy}} (which simply does a replace of
{{SubgraphStep}} with {{DseSubgraphStep}}. Regarding the {{SubgraphTest}}, this
is possible to change so its not using the structure API.
> Subgraph step requires the graph API
> ------------------------------------
>
> Key: TINKERPOP-1813
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1813
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.2.6
> Reporter: Bryn Cooke
> Assignee: Marko A. Rodriguez
> Priority: Minor
>
> SubgraphStrategy uses the graph API to create elements in the subgraph. If a
> graph does not fully support the graph/structure API this it won't work.
> Ideally the graph mutations should use the traversal API.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
