[ 
https://issues.apache.org/jira/browse/SOLR-14125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17002051#comment-17002051
 ] 

Noble Paul commented on SOLR-14125:
-----------------------------------

{quote}If I'm understanding the package loader correctly it will take a core 
reload to load the new functions. 
{quote}
Yes. New components require a core reload. However, changing the implementation 
of existing functions do not require a core reload.

However, in the future, I wish to whitelist a certain set of plugins which do 
not require core reload even for registering new plugins. It's fairly easy to 
register a new {{Expressible}} without reloading the core. I'm not going to 
take a look at that now. 

The workflow is as follows for a new type of {{Expressible}}
 * Create and install a new package which contains your shiny new streaming 
expressions
 * Invoke a {{create-expressible}} command on the config API. This internally 
results in a core reload

The work flow for updating an existing type of Expressible
 * Create and install a new package which contains your new version of 
{{Expressible}}
 * Invoke an update package command. This does not reload the cores

> <expressible> plugins must be hot loadable
> ------------------------------------------
>
>                 Key: SOLR-14125
>                 URL: https://issues.apache.org/jira/browse/SOLR-14125
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Noble Paul
>            Priority: Major
>              Labels: packagemanager
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> Today, the class is loaded at the core load time an a stong reference is 
> held. Package loading need it to be lazily loaded



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to