You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by "Alex O'Ree (JIRA)" <ju...@ws.apache.org> on 2015/02/16 21:13:11 UTC

[jira] [Updated] (JUDDI-915) investigate replication conflict handling

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

Alex O'Ree updated JUDDI-915:
-----------------------------
    Fix Version/s:     (was: 3.3)
                   3.3.1

> investigate replication conflict handling
> -----------------------------------------
>
>                 Key: JUDDI-915
>                 URL: https://issues.apache.org/jira/browse/JUDDI-915
>             Project: jUDDI
>          Issue Type: Task
>          Components: core
>            Reporter: Alex O'Ree
>            Assignee: Alex O'Ree
>             Fix For: 3.3.1
>
>
> there's a few scenarios in which data can be conflicted in replication
> -identify what the spec says about them
> related to custody transfer and replication
> if an identify entity is created at two different nodes (tmodel keygen) at the same time, then it should be conflicted due to node ownership. then try modifying one of them and confirm that the other is not changed and that custody is not transfer inadvertently. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)