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 2024/02/06 23:51:00 UTC

[jira] [Closed] (TINKERPOP-3049) onCreate for mergeV() doesn't handle Cardinality functions

     [ https://issues.apache.org/jira/browse/TINKERPOP-3049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephen Mallette closed TINKERPOP-3049.
---------------------------------------
    Fix Version/s: 4.0.0
                   3.7.2
       Resolution: Fixed

https://github.com/apache/tinkerpop/commit/66db18e17ad2937c71a3b2167fd0d7989ab2cbd7

> onCreate for mergeV() doesn't handle Cardinality functions
> ----------------------------------------------------------
>
>                 Key: TINKERPOP-3049
>                 URL: https://issues.apache.org/jira/browse/TINKERPOP-3049
>             Project: TinkerPop
>          Issue Type: Bug
>          Components: process
>    Affects Versions: 3.7.1
>            Reporter: Stephen Mallette
>            Assignee: Stephen Mallette
>            Priority: Critical
>             Fix For: 4.0.0, 3.7.2
>
>
> {{option(onCreate, 'k', set(1))}} doesn't do anything. it only works for {{onMatch}}. i think the reason was that the expectation was that providers would implement this functionality natively but that looking back, i don't think that's right. it should work out of the box even if it isn't performant.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)