Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Invalid
-
None
-
None
-
None
-
None
Description
The runtime libs loaded from remote URLs are loaded at core startup. This means we could make this classes visible to every component (including components in schema.xml)
So, if there are runtime libs with the "url" attribute the classloader will be created and that'll be the classloader for all components loaded in the core.
So what about legacy jars loaded from the .system collection?
They will be visible only to the components specially marked with runtimeLib="true" . Even those components can load classes from the jars loaded from remote urls
Attachments
Issue Links
- is related to
-
SOLR-13659 Refactor Cache config to lazily load the the class
- Resolved
-
SOLR-13565 Node level runtime libs loaded from remote urls
- Closed
-
SOLR-13637 Enable loading of plugins from the corecontainer memclassloader
- Resolved
- relates to
-
SOLR-13534 Dynamic loading of jars from a url
- Resolved