You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "Marko A. Rodriguez (JIRA)" <ji...@apache.org> on 2015/08/27 16:22:45 UTC
[jira] [Closed] (TINKERPOP3-744) Provide a mutation API
[ https://issues.apache.org/jira/browse/TINKERPOP3-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Marko A. Rodriguez closed TINKERPOP3-744.
-----------------------------------------
Resolution: Duplicate
This is related to TINKERPOP3-761.
[~dkuppitz] and [~mfrantz] ... What do you think on your respective proposal of TINKERPOP3-761 given [~bryncooke]'s comments.
> Provide a mutation API
> ----------------------
>
> Key: TINKERPOP3-744
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-744
> Project: TinkerPop 3
> Issue Type: Improvement
> Components: process
> Affects Versions: 3.0.0-incubating
> Reporter: Bryn Cooke
> Assignee: Marko A. Rodriguez
>
> Currently property mutations are restricted to setting a property to a fixed value and adding/removing.
> However for efficient gremlin server side mutations we will need more operations. For instance:
> * Incrementing the value of a property.
> * String manipulation.
> * Setting a property to be the soundex of another property.
> All these operations are available when updating a table using SQL.
> Currently this sort of thing is handled via sideeffect lambda, however this means deploying custom code to gremlin server instances.
> It would be great if we had a more fully featured mutations API. This would allow vendors to implement optimisations if their backend supports the mutation natively.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)