[
https://issues.apache.org/jira/browse/TINKERPOP3-694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14559781#comment-14559781
]
Marko A. Rodriguez commented on TINKERPOP3-694:
-----------------------------------------------
I added the following helper method to `Scope`.
https://github.com/apache/incubator-tinkerpop/blob/master/gremlin-core/src/main/java/org/apache/tinkerpop/gremlin/process/traversal/Scope.java#L38
This way all "selecting"-steps have the same pattern for grabbing from maps,
paths, and sideEffects. Both {{WhereStep}} and {{SelectStep}} now use this
utility. The new {{AddEdgeStep}} should leverage it.
> Bulk loading in TP
> ------------------
>
> Key: TINKERPOP3-694
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-694
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Reporter: Ran Magen
>
> Bulk loading can greatly increase performance in many backends, but there is
> no way for vendors to implement bulk loading in the TP API.
> As for how to do it, I was thinking a vendor could inherit from AddXStep, and
> implement bulk loading, enabling something like this:
> ArrayList<Object[]> vertices;
> __.inject(vertices).as("x").addV("x")
> Pros:
> 1. This seems like a standard approach to me, since vendors today batch up
> queries this way
> (https://github.com/thinkaurelius/titan/blob/titan09/titan-core/src/main/java/com/thinkaurelius/titan/graphdb/tinkerpop/optimize/TitanVertexStep.java#L72)
> 2. In contrast to the Graph.addVertex method (and the likes), using a
> traversal enables taking advantage of other strategies, like EventStrategy, a
> validation strategy, etc.
> Cons:
> 1. I don't think the mutating steps currently work with "x" (I'm not sure how
> you call this feature).
> 2. The steps are marked as final.
> Cheers,
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
