[
https://issues.apache.org/jira/browse/OAK-10462?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17771041#comment-17771041
]
Manfred Baedke edited comment on OAK-10462 at 10/2/23 10:57 AM:
----------------------------------------------------------------
I changed the title to better reflect the actual problem, which occurred when
an import operation happened on a node that was not versionable, but had some
leftover versioning properties set, probably because it had been versionable
before. Based on the existence of these properties, the VersionEditor decides
that the node in question is the sentinel node of a restore operation, which
might not be the case.
was (Author: baedke):
I changed the title to better reflect the actual problem, which occurred when
an import operation happened on a node that was not versionable, but had some
leftover versioning properties set, probably because it had been versionable
before. Based on the existence of these properties, the VersionEditor decides
that a restore operation is going on, which might not be the case.
> o.a.j.o.plugins.version.VersionEditor#propertyAdded() may mistakenly assume
> an ongoing restore operation.
> ---------------------------------------------------------------------------------------------------------
>
> Key: OAK-10462
> URL: https://issues.apache.org/jira/browse/OAK-10462
> Project: Jackrabbit Oak
> Issue Type: Bug
> Reporter: Rishabh Daim
> Assignee: Manfred Baedke
> Priority: Major
>
> The implementation always uses the value of jcr:versionHistory property but
> it needs to check whether the node is versionable or not as well.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
