[MGNLBACKUP-27] Jackrabbit 2.0 compatibility Created: 04/Jan/10  Updated: 29/Mar/22  Resolved: 04/Nov/15

Status: Closed
Project: Backup
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-2988 Preliminary support for jackrabbit 2 Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:
Team: Nucleus

 Description   

Issues mentioned in MAGNOLIA-2988 affects the backup module as well.
Also in light of the JR 2.0 and repo migration tool it provides we might want to re-implement backup module to use the said migration tool underneath.



 Comments   
Comment by Jan Haderka [ 31/Jan/11 ]
org.apache.jackrabbit.core.RepositoryCopier

/**
* Tool for backing up or migrating the entire contents (workspaces,
* version histories, namespaces, node types, etc.) of a repository to
* a new repository. The target repository (if it exists) is overwritten.
* <p>
* No cluster journal records are written in the target repository. If the
* target repository is clustered, it should be the only node in the cluster.
* <p>
* The target repository needs to be fully reindexed after the copy operation.
* The static copy() methods will remove the target search index folders from
* their default locations to trigger automatic reindexing when the repository
* is next started.
*
* @since Apache Jackrabbit 1.6
*/
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Sun Feb 11 23:24:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.