[SOLR-8311] SolrCoreAware and ResourceLoaderAware lifecyel is fragile - particularly with objects that can be created after SolrCore is live

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Assignee: Unassigned
• Reporter: Chris M. Hostetter
• Created: 18/Nov/15 17:59
• Updated: 26/Sep/23 12:43

Description

In general, the situation of when/how ResourceLoaderAware & SolrCoreAware instances are "informed" of the ResourceLoader & SolrCore is very kludgy and involves a lot of special casees.

For objects initialized before the SolrCore goes "live", SolrResourceLoader tracks these instances internally, and calls inform() on all of them – but for instances created after the SolrCore is live (ex: schema pieces created via runtime REST calls), SolrResourceLoader does nothing to ensure they are later informed (and typically can't because that must happen after whatever type specific 'init' logic takes place). So there is a lot of special case handling to call inform methods sprinkled through out he code

This issue serves as a refrence point to track/link various comments on the situation, and to cite in comments warning developers about how finicky it is to muck with the list of SolrCoreAware & ResourceLoaderAware allowed implementations.

Issue Links

• is related to: SOLR-16998 Adopt JSR-330 dependency injection
• is related to: SOLR-12886 QParserPlugin to support SolrCoreAware
• is related to: SOLR-11735 TransformerFactory to support SolrCoreAware
• relates to: SOLR-8280 Schemaless features don't work reliably with SolrCoreAware sim factory -- example: SchemaSimilarityFactory
• mentioned in: Page Loading...