You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "stephen mallette (JIRA)" <ji...@apache.org> on 2018/09/14 13:13:00 UTC
[jira] [Closed] (TINKERPOP-2036) Make GraphReader and GraphWriter
more friendly to GraphTraversalSource
[ https://issues.apache.org/jira/browse/TINKERPOP-2036?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stephen mallette closed TINKERPOP-2036.
---------------------------------------
Resolution: Won't Do
Fix Version/s: (was: 3.4.0)
1 hour in and.................hornets nest - bye felicia
> Make GraphReader and GraphWriter more friendly to GraphTraversalSource
> ----------------------------------------------------------------------
>
> Key: TINKERPOP-2036
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2036
> Project: TinkerPop
> Issue Type: Improvement
> Components: io
> Affects Versions: 3.4.0
> Reporter: stephen mallette
> Assignee: stephen mallette
> Priority: Major
> Labels: deprecation
>
> We've been migrating users further and further away from the Graph API. The recently added {{io()}} step helps with that immensely. In that process, the {{GraphReader}} and {{GraphWriter}} interfaces probably should have went a step further to include an overloads for {{readGraph()}} and {{writeGraph()}} that used a {{GraphTraversalSource}} with deprecation for the {{Graph}} versions. Again, we don't need to remove these methods any time soon, but the preference should be toward preferring {{GraphTraversalSource}} when possible. This can be implemented as a non-breaking change to the API for those who have their own implementations of these interfaces.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)