You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "Ishan Chattopadhyaya (Jira)" <ji...@apache.org> on 2019/10/06 15:17:00 UTC
[jira] [Resolved] (SOLR-13564) Runtime libs loaded from remote URLs
should be available to all components
[ https://issues.apache.org/jira/browse/SOLR-13564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ishan Chattopadhyaya resolved SOLR-13564.
-----------------------------------------
Resolution: Invalid
There are changes to design (SOLR-13661) and this work is no longer needed. Separate sub-tasks might cover some of this work here. Thanks [~noble.paul].
> Runtime libs loaded from remote URLs should be available to all components
> --------------------------------------------------------------------------
>
> Key: SOLR-13564
> URL: https://issues.apache.org/jira/browse/SOLR-13564
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Noble Paul
> Priority: Major
>
> 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
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org