[jira] [Commented] (JCRVLT-105) Use Node.setPrimaryType() when changing primary type.

["Carsten Ziegeler (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCRVLT-105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14956266#comment-14956266 ] 

Carsten Ziegeler commented on JCRVLT-105:
-----------------------------------------

Thanks [~anchela] - I think apart from the node type there are other criterias where this happens (I think something with UUID handling and maybe others). Hopefully these can be solved somehow as well and all this moving back and forth can be completely avoided

> Use Node.setPrimaryType() when changing primary type.
> -----------------------------------------------------
>
>                 Key: JCRVLT-105
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-105
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>            Reporter: Carsten Ziegeler
>            Assignee: Tobias Bocanegra
>             Fix For: 3.1.26
>
>
> Vlt was written for Jackrabbit 2, I assume with Oak some operations can be optimized. We just stumpled across some code which changes the node type of a node on a package import: it basically does this by moving all child nodes to a temp node, deleting the node, recreating it with the new node type and then moving all child nodes back. If the tree below that node is large, this is a very heavy and expensive operation. Afaik, node type can be changed with Oak.
> There might be other optimizations like this



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