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/06/28 14:27:00 UTC

[jira] [Commented] (TINKERPOP-1174) addVertex(Map properties) method

    [ https://issues.apache.org/jira/browse/TINKERPOP-1174?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16526355#comment-16526355 ] 

stephen mallette commented on TINKERPOP-1174:
---------------------------------------------

I come back to this again.... I don't see us implementing this in TinkerPop 3.x - multi/meta properties sorta hinder this approach to the API because you can't easily express them in a {{Map}}. I think we should just close this with the idea that it will be considered/possible in TinkerPop 4.x when multi/meta properties are likely a thing of the past.

> 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
>            Priority: Major
>
> 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
(v7.6.3#76005)