将Jackrabbit 1.3升级到Jackrabbit 2.1.1

Question

在我的项目中，我需要将Jackrabbit 1.3更改为Jackrabbit 2.1.1。我的工作是处理查询。如果索引格式和查询格式有变化，请给我建议。Lucene 2.4在JackRabb2.1.1中使用，而在JackRabb1.3中使用Lucene 2.2。

Answer 1

让我们将您的升级分为以下几个部分：

• 从1.3升级到1.5 (请参见Class IndexMigration)：

IndexMigration实现了一个实用程序，可以将JackRabb1.4.x索引迁移到1.5版。在1.4.x之前的版本中，索引使用字符'‘来分隔属性名称和值。从Lucene 2.3开始，这不再起作用。参见LUCENE-1221。杰克兔>= 1.5使用字符'[‘作为分隔符。每当从磁盘打开索引时，都会运行一次快速检查，以确定是否需要迁移。另请参阅JCR-1363以了解更多细节。

• 从1.5升级到2.0.0 (请参见RELEASE-NOTES.txt)：

向后兼容性

2.0是一个，旨在与现有的JackRabb1.x客户端和存储库兼容。实现此目标的主要exceptions包括：

- Removal of deprecated classes and features. Jackrabbit 2.0 is not   backwards compatible with client code that used classes or features   that had been deprecated during the 1.x release cycle. Most notably   the temporary org.apache.jackrabbit.api.jsr283 interfaces have been   removed in favor of the official JCR 2.0 API in javax.jcr.
- Repositories that have used the new JSR 283 security features included   as a development preview in Jackrabbit 1.5 and 1.6 may face problems   when upgrading to Jackrabbit 2.0. See especially [JCR-1944](https://issues.apache.org/jira/browse/JCR-1944) and [JCR-2313](https://issues.apache.org/jira/browse/JCR-2313)   for more details.
- The JCR-RMI layer no longer implements the Jackrabbit API extensions.   Code that uses JCR-RMI with distributed transactions or for administration   operations like creating workspaces or registering node types needs to   be updated accordingly.
- The JCR-RMI layer in Jackrabbit 2.0 only supports JCR 2.0 repositories.   To access a JCR 1.0 repository implementation like Jackrabbit 1.x over   RMI, you need to use the 1.x versions of JCR-RMI.

• 从2.0.0升级到2.1.1 (2.x分支的定位是为了拥有稳定的应用编程接口)：

这是Apache Jackrabbit 2.0.0，它是一个完全兼容的，并且是内容存储库for Java Technology API2.0版的生产就绪实现

另请参阅Jackrabbit和Lucene API的兼容性表。

Answer 2

有多种方法可以从Jackrabbit 1.x迁移到2.x。也许最好的文档可以在Backup and Migration页面的Jackrabbit Wiki中找到。