Update bulk import/export section for graph providers given g.io() CTR
Project: http://git-wip-us.apache.org/repos/asf/tinkerpop/repo Commit: http://git-wip-us.apache.org/repos/asf/tinkerpop/commit/a5d1aa66 Tree: http://git-wip-us.apache.org/repos/asf/tinkerpop/tree/a5d1aa66 Diff: http://git-wip-us.apache.org/repos/asf/tinkerpop/diff/a5d1aa66 Branch: refs/heads/TINKERPOP-1967 Commit: a5d1aa660b28a5c126b3f7dec945f8558d42816c Parents: 72b264d Author: Stephen Mallette <sp...@genoprime.com> Authored: Mon Aug 6 07:46:58 2018 -0400 Committer: Stephen Mallette <sp...@genoprime.com> Committed: Mon Aug 6 07:46:58 2018 -0400 ---------------------------------------------------------------------- docs/src/dev/provider/index.asciidoc | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/tinkerpop/blob/a5d1aa66/docs/src/dev/provider/index.asciidoc ---------------------------------------------------------------------- diff --git a/docs/src/dev/provider/index.asciidoc b/docs/src/dev/provider/index.asciidoc index ab57020..49bc7c7 100644 --- a/docs/src/dev/provider/index.asciidoc +++ b/docs/src/dev/provider/index.asciidoc @@ -620,12 +620,17 @@ reason to implement this interface. ==== Bulk Import Export When it comes to doing "bulk" operations, the diverse nature of the available graph databases and their specific -capabilities, prevents TinkerPop from doing a good job of generalizing that capability well. TinkerPop refers users to -the bulk import/export facilities of specific graph providers as they tend to be more efficient and easier to use than -the options TinkerPop has tried to generalize in the past. +capabilities, prevents TinkerPop from doing a good job of generalizing that capability well. TinkerPop thus maintains +two positions on the concept of import and export: -That said, for graph providers that don't have a special bulk loading feature, they can get a basic bulk loader from -TinkerPop using the link:http://tinkerpop.apache.org/docs/x.y.z/reference/#clonevertexprogram[CloneVertexProgram]. +1. TinkerPop refers users to the bulk import/export facilities of specific graph providers as they tend to be more +efficient and easier to use than the options TinkerPop has tried to generalize in the past. +2. TinkerPop encourages graph providers to expose those capabilities via `g.io()` and the `IoStep` by way of a +`TraversalStrategy`. + +That said, for graph providers that don't have a special bulk loading feature, they can either rely on the default +OLTP (single-threaded) `GraphReader` and `GraphWriter` options that are embedded in `IoStep` or get a basic bulk loader +from TinkerPop using the link:http://tinkerpop.apache.org/docs/x.y.z/reference/#clonevertexprogram[CloneVertexProgram]. Simply provide a `InputFormat` and `OutputFormat` that can be referenced by a `HadoopGraph` instance as discussed in the link:http://tinkerpop.apache.org/docs/x.y.z/reference/#clonevertexprogram[Reference Documentation].