[
https://issues.apache.org/jira/browse/SOLR-13661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16924759#comment-16924759
]
Jan Høydahl commented on SOLR-13661:
------------------------------------
So here's the branch [https://github.com/cominvent/lucene-solr/tree/pf4j]
{quote}I think we can leverage the package discovery dependency management
done in your PoC. My efforts are mainly focussed on efficiently
loading/reloading the binaries inside Solr so that there is no disruption to
the cluster and the requests in flight.
{quote}
Yea, the PF4J approach does not try to solve the hot loading problem, only the
discovery, repository, packaging, dependency resolution and class-loading
cycle. Then you need a restart of the app to be sure that the new/changed jars
gets loaded, due to how the Java class loaders work. So my POC kind of works
for dynamically *adding* new packages without restart but not for upgrading.
In one way I like the cold workflow (install packages without needing Solr to
be running) since it is by definition compatible with the Ansible / Chef /
Dockerfile workflow of deploying software. So if we could offer best of both
worlds that would be great - i.e. a workflow where you could place plugin jars
or command JSON snippets in some location (local/shared folder or some https
location) and running Solr would automatically execute this on startup and
through polling when running. Possible?
> A package management system for Solr
> ------------------------------------
>
> Key: SOLR-13661
> URL: https://issues.apache.org/jira/browse/SOLR-13661
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Priority: Major
> Labels: package
>
> Solr needs a unified cohesive package management system so that users can
> deploy/redeploy plugins in a safe manner. This is an umbrella issue to
> eventually build that solution
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]