You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tinkerpop.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/03/02 16:20:00 UTC

[jira] [Commented] (TINKERPOP-2681) Create merge() step to codify best practice for upsert pattern

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

ASF GitHub Bot commented on TINKERPOP-2681:
-------------------------------------------

FlorianHockmann opened a new pull request #1579:
URL: https://github.com/apache/tinkerpop/pull/1579


   Using `=>` instead of `=` also makes these properties instead of fields which is more consistent with the other properties there.
   
   These directions were only added in #1555 which wasn't released yet, so this is not breaking anything.
   
   VOTE +1


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@tinkerpop.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Create merge() step to codify best practice for upsert pattern
> --------------------------------------------------------------
>
>                 Key: TINKERPOP-2681
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-2681
>             Project: TinkerPop
>          Issue Type: Improvement
>          Components: language, process
>    Affects Versions: 3.5.1
>            Reporter: Dave Bechberger
>            Assignee: Stephen Mallette
>            Priority: Major
>             Fix For: 3.6.0
>
>
> Create a step that codifies the best practice for the upsert functionality into a single step to make it easier to use, more discoverable, and easier for implementers to optimize.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)