[
https://issues.apache.org/jira/browse/TINKERPOP-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15905622#comment-15905622
]
stephen mallette commented on TINKERPOP-1174:
---------------------------------------------
There is also now the technical reason to look to implement this - scripts with
many parameters are more costly to compile than those with fewer, so this:
{code}
g.addV("x1",x1, "x2",x2, "x3",x3, .....)
{code}
would compile significantly slower than:
{code}
m = ["x1":x1, "x2":x2, "x3":x3, .....]
g.addV(m)
{code}
> addVertex(Map properties) method
> --------------------------------
>
> Key: TINKERPOP-1174
> URL: https://issues.apache.org/jira/browse/TINKERPOP-1174
> Project: TinkerPop
> Issue Type: Improvement
> Components: process
> 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.15#6346)
