You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2015/11/18 18:59:11 UTC

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

Hoss Man created SOLR-8311:
------------------------------

             Summary: SolrCoreAware and ResourceLoaderAware lifecyel is fragile - particularly with objects that can be created after SolrCore is live
                 Key: SOLR-8311
                 URL: https://issues.apache.org/jira/browse/SOLR-8311
             Project: Solr
          Issue Type: Bug
            Reporter: Hoss Man



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.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org