The Content Feeder can feed content issues into the Solr index "studio" now, so that it becomes possible to search for content items with issues in the Studio library or using native Solr queries. This feature is enabled by default in 2104.1 and 2104.2, but will be disabled by default in 2104.3+. The feature builds on Solr Nested Document Support and the new Solr schema fields \_root\_ and \_nest\_path\_ for the Content Feeder index, as described in the release note CMS-10950. To use this feature, the mentioned Solr fields must be added, and the studio index must be recreated from scratch. You can disable this feature, if you want to keep an existing index without reindexing. The configuration will be changed in 2104.3+ to be disabled by default, so that the default configuration does not require recreation of existing indexes.

Issue feeding also causes additional work in the Content Feeder , which negatively impacts its throughput. If you don't want to search for content issues, the new functionality can be disabled by setting the configuration property feeder.content.issues.index=false . You may also want to disable issue feeding, if you have customized the Content Feeder to feed another external system instead of using the default integration for Solr. If not disabled, custom implementations of the com.coremedia.cap.feeder.index.Indexer interface may have to be adapted to either ignore or handle content issues.

The Content Feeder uses all validator instances that are available in its Spring application context. In the Blueprint, all Studio content validators have been registered with the Content Feeder . Custom validation logic can be integrated into the Content Feeder in the same way as into the Studio Server .

Note, that not all types of issues are always up-to-date in the index. The Content Feeder recomputes and reindexes content issues periodically, by default once a day. This happens with lower priority and does not block feeding of editorial changes. Depending on the size of the content repository, it may still make sense to fine-tune the configuration.

For more details, see the Search Manual's new section "Searching for Content | Content Issues".

Solr Configuration Changes

If you've customized the Solr configuration, make sure to apply the changes from the Blueprint Solr configuration files in apps/solr/modules/search/solr-config/src/main/app/configsets

The following new fields were added to the Solr studio index in content/conf/schema.xml :

The field "issuesUpdated" contains the date when indexed content issues were computed. The other fields are used to describe content issues in nested Solr documents of the corresponding content items.

(CMS-18432)