[
https://issues.apache.org/jira/browse/TINKERPOP-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16559143#comment-16559143
]
ASF GitHub Bot commented on TINKERPOP-1996:
-------------------------------------------
Github user twilmes commented on a diff in the pull request:
https://github.com/apache/tinkerpop/pull/893#discussion_r205649402
--- Diff: docs/src/upgrade/release-3.4.x.asciidoc ---
@@ -65,6 +65,33 @@ release where breaking changes are allowed.
See:
link:https://issues.apache.org/jira/browse/TINKERPOP-1975[TINKERPOP-1975],
link:http://tinkerpop.apache.org/docs/3.4.0/reference/#with-step[Reference
Documentation]
+==== io() Step
+
+There have been some important changes to IO operations for reading and
writing graph data. The use of `Graph.io()`
+has been deprecated to further remove dependence on the Graph (Structure)
API for users and to extend these basic
+operations to GLV users by making these features available as part of the
Gremlin language.
+
+It is now possible to simply use Gremlin:
+
+[source,groovy]
+----
+graph = ...
+g = graph.traversal()
+g.io(someInputFile).read().iterate()
+g.io(someOutputFile).write().iterate()
+----
+
+While `io()` step is still single-threaded for OLTP style loading, it can
be utilized in conjunction with OLAP which
--- End diff --
Small nit, in spots I think it's referenced as `io()` step in others
`io()`-step. Might be good to stick with one or another. It looks like the `-`
style is prevalent in the docs.
> Introduce read() and write() steps
> ----------------------------------
>
> Key: TINKERPOP-1996
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1996
> Project: TinkerPop
> Issue Type: Improvement
> Components: io, process
> Affects Versions: 3.4.0
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Major
> Labels: deprecation
> Fix For: 3.4.0
>
>
> Make {{read()}} and {{write()}} steps the replacements for {{graph.io()}} so
> that these operations are simply part of the Gremlin language.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
