You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Alex Parvulescu (JIRA)" <ji...@apache.org> on 2015/07/28 11:31:04 UTC
[jira] [Comment Edited] (OAK-3130) ReferenceEditor may not enforce
referential integrity
[ https://issues.apache.org/jira/browse/OAK-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14644094#comment-14644094 ]
Alex Parvulescu edited comment on OAK-3130 at 7/28/15 9:30 AM:
---------------------------------------------------------------
merged to 1.2 with http://svn.apache.org/r1693042, and to 1.0 with http://svn.apache.org/r1693049
was (Author: alex.parvulescu):
merged to 1.2 with http://svn.apache.org/r1693042
> ReferenceEditor may not enforce referential integrity
> -----------------------------------------------------
>
> Key: OAK-3130
> URL: https://issues.apache.org/jira/browse/OAK-3130
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: jcr
> Affects Versions: 1.2.3, 1.3.3, 1.0.17
> Reporter: Marcel Reutegger
> Assignee: Marcel Reutegger
> Fix For: 1.2.4, 1.3.4, 1.0.18
>
> Attachments: OAK-3130.patch
>
>
> VersionHistory.removeVersion() allows to remove a version of a checked in node still referencing that version. This results in a dangling base version.
> This is caused by a more general issue in the ReferenceEditor, which does not enforce referential integrity in some cases.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)