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 "Tomek Rękawek (JIRA)" <ji...@apache.org> on 2016/01/07 12:37:39 UTC
[jira] [Updated] (OAK-3844) Better support for versionable nodes
without version histories
[ https://issues.apache.org/jira/browse/OAK-3844?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomek Rękawek updated OAK-3844:
-------------------------------
Description:
One of the customers reported following exception that has been thrown during the migration:
{noformat}
Caused by: java.lang.IllegalStateException: This builder does not exist: 95a5253f-d37b-4e88-a4b4-0721530344fc
at com.google.common.base.Preconditions.checkState(Preconditions.java:150)
at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:506)
at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:522)
at org.apache.jackrabbit.oak.upgrade.version.VersionableEditor.setVersionablePath(VersionableEditor.java:148)
at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore.merge(SegmentNodeStore.java:226)
...
at org.apache.jackrabbit.oak.upgrade.RepositoryUpgrade.copy(RepositoryUpgrade.java:486)
{noformat}
It seems that the node with reported UUID has primary type inheriting from {{mix:versionable}}, but there is no appropriate version history in the version storage.
Obviously this means that there's something wrong with the repository. However, I think that the migration process shouldn't fail, but proceed silently.
was:
One of the customers reported following exception that has been thrown during the migration:
{noformat}
Caused by: java.lang.IllegalStateException: This builder does not exist: 95a5253f-d37b-4e88-a4b4-0721530344fc
at com.google.common.base.Preconditions.checkState(Preconditions.java:150)
at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:506)
at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:522)
at org.apache.jackrabbit.oak.upgrade.version.VersionableEditor.setVersionablePath(VersionableEditor.java:148)
at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore.merge(SegmentNodeStore.java:226)
...
at org.apache.jackrabbit.oak.upgrade.RepositoryUpgrade.copy(RepositoryUpgrade.java:486)
{noformat}
It seems that the node with reported UUID has primary type inheriting from {{mix:versionable}}, but there is no appropriate version history in the version storage.
Obviously this means that there's something wrong with the repository. However, I think that the migration process shouldn't fail in this case but log a warning and proceed.
> Better support for versionable nodes without version histories
> --------------------------------------------------------------
>
> Key: OAK-3844
> URL: https://issues.apache.org/jira/browse/OAK-3844
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: upgrade
> Affects Versions: 1.3.13
> Reporter: Tomek Rękawek
> Fix For: 1.4
>
>
> One of the customers reported following exception that has been thrown during the migration:
> {noformat}
> Caused by: java.lang.IllegalStateException: This builder does not exist: 95a5253f-d37b-4e88-a4b4-0721530344fc
> at com.google.common.base.Preconditions.checkState(Preconditions.java:150)
> at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:506)
> at org.apache.jackrabbit.oak.plugins.memory.MemoryNodeBuilder.setProperty(MemoryNodeBuilder.java:522)
> at org.apache.jackrabbit.oak.upgrade.version.VersionableEditor.setVersionablePath(VersionableEditor.java:148)
> at org.apache.jackrabbit.oak.plugins.segment.SegmentNodeStore.merge(SegmentNodeStore.java:226)
> ...
> at org.apache.jackrabbit.oak.upgrade.RepositoryUpgrade.copy(RepositoryUpgrade.java:486)
> {noformat}
> It seems that the node with reported UUID has primary type inheriting from {{mix:versionable}}, but there is no appropriate version history in the version storage.
> Obviously this means that there's something wrong with the repository. However, I think that the migration process shouldn't fail, but proceed silently.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)