[
https://issues.apache.org/jira/browse/TINKERPOP3-744?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bryn Cooke updated TINKERPOP3-744:
----------------------------------
Description:
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.
was:
Currently property mutations to elements 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.
> Provide a mutation API
> ----------------------
>
> Key: TINKERPOP3-744
> URL: https://issues.apache.org/jira/browse/TINKERPOP3-744
> Project: TinkerPop 3
> Issue Type: New Feature
> Components: process
> Affects Versions: 3.0.0.GA
> 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)
