Solr 的 DatePointField 是 TrieDateField 的直接替代品吗？
Is Solr's DatePointField a drop-in replacement for TrieDateField?
我在 Solr 7.5 安装中收到一些弃用警告：
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieIntField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieFloatField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieLongField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieDoubleField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieDateField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.LatLonType]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:37 Solr loaded a deprecated plugin/analysis class [solr.WordDelimiterFilterFactory]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:37 Solr loaded a deprecated plugin/analysis class [solr.SynonymFilterFactory]. Please consult documentation how to replace it accordingly. []
documentation 只是告诉我 Trie* 已被弃用，我找不到除以下以外的迁移指南：
TrieDateField: Deprecated. Use DatePointField instead.
我可以只替换 Trie* 字段类型 类 并更新我的 运行 Solr 实例上的架构吗？
那么这里提到的非 Trie 字段呢？
它们是否会减少替换取决于您的使用情况，但是是的，它们应该做同样的事情，只是效率更高。但是，您 将 必须在更改类型后重新编制索引 - 您不能只更改架构并假设现有数据将按预期工作（因为您最终会在执行遍历文档的操作时使用不同的数据类型）。
对于过滤器，它们已替换为对应的图形（SynonymGraphFilter 和 WordDelimiterGraphFilter）。
LatLonType 已替换为 LatLonPointSpatialField。
您可以看到这些列表 changes in Major Changes in Solr 7。
If you are using Trie* fields in your schema, you should consider moving to PointFields as soon as feasible. Changing to the new PointField types will require you to re-index your data.
我在 Solr 7.5 安装中收到一些弃用警告：
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieIntField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieFloatField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieLongField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieDoubleField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.TrieDateField]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:36 Solr loaded a deprecated plugin/analysis class [solr.LatLonType]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:37 Solr loaded a deprecated plugin/analysis class [solr.WordDelimiterFilterFactory]. Please consult documentation how to replace it accordingly. []
[ WARN] 16:38:37 Solr loaded a deprecated plugin/analysis class [solr.SynonymFilterFactory]. Please consult documentation how to replace it accordingly. []
documentation 只是告诉我 Trie* 已被弃用，我找不到除以下以外的迁移指南：
TrieDateField: Deprecated. Use DatePointField instead.
我可以只替换 Trie* 字段类型 类 并更新我的 运行 Solr 实例上的架构吗？
那么这里提到的非 Trie 字段呢？
它们是否会减少替换取决于您的使用情况，但是是的，它们应该做同样的事情，只是效率更高。但是，您 将 必须在更改类型后重新编制索引 - 您不能只更改架构并假设现有数据将按预期工作（因为您最终会在执行遍历文档的操作时使用不同的数据类型）。
对于过滤器，它们已替换为对应的图形（SynonymGraphFilter 和 WordDelimiterGraphFilter）。
LatLonType 已替换为 LatLonPointSpatialField。
您可以看到这些列表 changes in Major Changes in Solr 7。
If you are using Trie* fields in your schema, you should consider moving to PointFields as soon as feasible. Changing to the new PointField types will require you to re-index your data.