[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 1.3.10)
> Incorrect handling of addExistingNode conflict in NodeStore
> ---
>
> Key: OAK-1550
> URL: https://issues.apache.org/jira/browse/OAK-1550
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: mongomk
>Reporter: Michael Dürig
>Assignee: Marcel Reutegger
> Labels: concurrency, observation, technical_debt
>
> {{MicroKernel.rebase}} says: "addExistingNode: node has been added that is
> different from a node of them same name that has been added to the trunk."
> However, the {{NodeStore}} implementation
> # throws a {{CommitFailedException}} itself instead of annotating the
> conflict,
> # also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 1.3.5)
1.3.6
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Labels: concurrency, observation, technical_debt
Fix For: 1.3.6
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 1.3.1)
1.3.5
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Labels: concurrency, observation, technical_debt
Fix For: 1.3.5
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Labels: concurrency observation technical_debt (was: concurrency
observation)
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Labels: concurrency, observation, technical_debt
Fix For: 1.3.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-1550:
---
Labels: concurrency observation (was: technical_debt)
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Labels: concurrency, observation
Fix For: 1.3.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-1550:
---
Labels: technical_debt (was: )
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Labels: technical_debt
Fix For: 1.3.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-1550:
---
Fix Version/s: (was: 1.4)
1.3.1
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 1.3.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 1.2)
1.4
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 1.4
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 1.1.1)
1.2
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 1.2
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amit Jain updated OAK-1550:
---
Fix Version/s: (was: 1.1)
1.1.1
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 1.1.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcel Reutegger updated OAK-1550:
--
Fix Version/s: (was: 0.20)
1.1
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 1.1
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Updated] (OAK-1550) Incorrect handling of addExistingNode conflict in NodeStore
[
https://issues.apache.org/jira/browse/OAK-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Marth updated OAK-1550:
---
Assignee: Marcel Reutegger
Incorrect handling of addExistingNode conflict in NodeStore
---
Key: OAK-1550
URL: https://issues.apache.org/jira/browse/OAK-1550
Project: Jackrabbit Oak
Issue Type: Bug
Components: mongomk
Reporter: Michael Dürig
Assignee: Marcel Reutegger
Fix For: 0.20
{{MicroKernel.rebase}} says: addExistingNode: node has been added that is
different from a node of them same name that has been added to the trunk.
However, the {{NodeStore}} implementation
# throws a {{CommitFailedException}} itself instead of annotating the
conflict,
# also treats the equal childs with the same name as a conflict.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
