While such query conditions never matched anything, they might be used in project code, but will cause errors now. The removal of the catch-all dynamicfield means, that it is no longer possible to use undefined Solr field names in Solr queries. This field is necessary to support queries from old CAE applications, and can be removed otherwise. , a deprecated field "1" of type "ignored" was added. This field is necessary to support queries from old Studio applications, and can be removed otherwise. , a deprecated field "INVALID" of type "ignored" was added. This was necessary to workaround a Solr bug (SOLR-15018). The catch-all dynamicfield "*" of type "ignored" has been removed. Adding these fields to an existing index must be avoided, as it can cause index inconsistencies. If you add these fields, you must reindex from scratch. Do not add these fields if you are not planning to reindex. The addition of new Solr fieldsÄescribed below requires complete reindexing from scratch but you only need to add them, if you actually use Solr nested documents. If you've customized the Solr configuration, make sure to apply the changes from Blueprint Solr configuration files inĪpps/solr/modules/search/solr-config/src/main/app/configsets This change requires manual upgrade steps, but reindexing is only required if Solr nested documents are actually being used. For this support, some changes were necessary in the Feeder API and Solr configuration. To set data for indexing nested documents. Support optional indexing of Solr nested documents now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |