You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Matthias Broecheler (JIRA)" <ji...@apache.org> on 2016/09/28 16:20:20 UTC
[jira] [Reopened] (TINKERPOP-1174) addVertex(Map properties) method
[ https://issues.apache.org/jira/browse/TINKERPOP-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthias Broecheler reopened TINKERPOP-1174:
--------------------------------------------
It seems like this was closed on the grounds that one should use the traversal ``addV`` instead of the graph ``addVertex`` method.
In that case, we should add the Map overload to ``addV`` - the usability / user convenience argument remains the same and a strong one (as confirmed by Peter)
> addVertex(Map properties) method
> --------------------------------
>
> Key: TINKERPOP-1174
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1174
> Project: TinkerPop
> Issue Type: Improvement
> Components: structure
> Affects Versions: 3.1.1-incubating
> Reporter: Matthias Broecheler
> Assignee: stephen mallette
>
> which overloads the other {{addVertex(Object... properties)}} method with a map based version (of key-value pairs).
> Having this alternative to addVertex is nice because:
> 1) It allows you to submit a map when adding vertices on remote graphs via drivers. Right now, you have to convert the properties to an array which is awkward and unnecessary
> 2) It would work well with groovy's map based syntax so one can write:
> {{g.addVertex( key1 : "value1", key2: "value2")}}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)