[
https://issues.apache.org/jira/browse/TINKERPOP-2417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17193562#comment-17193562
]
Stephen Mallette commented on TINKERPOP-2417:
---------------------------------------------
I would prefer not to remove the deprecation as I'd like folks who can use
{{g.io(String)}} to find it and do so - perhaps we could add a comment that
clarifies that the "stream" options aren't available with {{g.io()}} if you
think that is helpful. There is no intention to remove the deprecated methods
for {{Graph.io()}} until we more fully satisfy functionality of {{g.io()}} so
that is safe through 3.5.x at least. You can still create a custom
reader/writer for {{g.io()}} but you can't make it use the {{InputStream}} or
{{OutputStream}} of your choice.
> Add possibility to supply io step with InputStream instead of a file path
> -------------------------------------------------------------------------
>
> Key: TINKERPOP-2417
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2417
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Reporter: Oleksandr Porunov
> Priority: Major
>
> Currently it is possible to supply *io* step with file path to read a file
> from file system.
> It would be very convenient if we would be able to read files from input
> stream instead of file path.
> For example, it could look something like:
> *g.io(graphSonInputStream).with(IO.reader, IO.graphson).read().iterate()*
> Of course it wouldn't work as expected if we would use *write* instead of
> read here because we won't be able to write to the input stream. Thus, we can
> fail fast if the user supplied an input stream into the *io* step but tried
> to use *write*.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
