SOLR 1.3 和 SOLR 3.4 之间是否存在主要的架构差异？
有一些使用 SOLR 1.3 的旧版 (DNN) 站点，我希望将它们升级到 SOLR 3.4。模式文件中是否有任何核心配置更改会阻止模式的简单传输和重新索引？
There are some legacy (DNN) sites using SOLR 1.3 and I'd like to get them to SOLR 3.4. Are there any core configuration changes in the schema files that would prevent a simple transfer of the schema and re-indexing?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我认为 3.4 版本有最剧烈的变化，因为那时 Solr-trunk 合并到 Lucene trunk 中，使两个存储库更加同步。从发行说明中我可以看出，您必须注意一件主要的事情。 Namley 索引格式已更改，因此您肯定需要重新索引。
我能找到的唯一的另一件事是不再忽视矛盾的设置。
我建议您升级并尝试快速重新索引。如果没有发生灾难性的故障，您很可能是安全的。
包括我检查的发行说明和一些我发现有趣的摘录：
1.4 发行说明
3.4 发行说明
Lucene 索引格式已更改，因此一旦升级，
以前版本的 Solr 将不再能够读取您的索引。
在主/从配置中，所有搜索器/从属设备都应升级
师父面前。如果要先更新 master，则较旧的
搜索者将无法读取新的索引格式。
以前版本的 Solr 默默地允许并忽略一些矛盾
schema.xml 中指定的属性。例如：
indexed="false" omitNorms="false"
indexed="false" omitTermFreqAndPositions="false"
字段属性验证现已修复，以确保
像这样的矛盾现在会产生错误消息。如果用户
现有的模式可以生成这些新的“冲突的”之一
非索引字段的“假”字段选项”错误消息
可以安全地删除冲突的“省略*”属性，或将其更改为
“true”表示与以前的 Solr 版本保持一致的行为。
I think version 3.4 has the most drastic changes since that is when Solr-trunk merged into Lucene trunk making the two repos more in sync. From what I can see from the release notes you have to watch out for one primary thing. Namley the index format has changed so you definitely need to reindex.
The only other thing I could find relates to no longer ignoring contradictory settings.
I would recommend you to just upgrade and try to do a quick reindex. If nothing fails catastrophically you are most likely safe.
Including the release notes I checked and some extracts I found interesting:
1.4 release notes
3.4 release notes
The Lucene index format has changed and as a result, once you upgrade,
previous versions of Solr will no longer be able to read your indices.
In a master/slave configuration, all searchers/slaves should be upgraded
before the master. If the master were to be updated first, the older
searchers would not be able to read the new index format.
Previous versions of Solr silently allow and ignore some contradictory
properties specified in schema.xml. For example:
indexed="false" omitNorms="false"
indexed="false" omitTermFreqAndPositions="false"
Field property validation has now been fixed, to ensure that
contradictions like these now generate error messages. If users
have existing schemas that generate one of these new "conflicting
'false' field options for non-indexed field" error messages the
conflicting "omit*" properties can safely be removed, or changed to
"true" for consistent behavior with previous Solr versions.