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

Jan Høydahl commented on SOLR-13661:
------------------------------------

{quote}Our users mostly write plugins and deploy their plugins. Third party 
plugins are very few. So everyone who wishes to use your solution will have to 
write extra code to comply with your package format
{quote}
The only poll I have seen in the Solr community on plugin usage is my own 
([https://www.slideshare.net/janhoy/solrs-missing-plugin-ecosystem/17]) which 
shows that several 3rd party plugins are in use and only four of the 
respondents deploy custom plugins:
 !plugin-usage.png|width=800!

The plugin architecture needs to be designed with main focus on typical use, 
and then add more esoteric features later. In my eyes multi tenancy and 
different versions of the same plugins for different collections is *not* the 
80% use case. So we need to make it dead simple for the casual Solr OPS person 
to discover, install and manage plugins. And for the developers we need to make 
it convenient to publish their plugins into one of our official repositories or 
to publish their own repo from a GitHub URL. For the large enterprise with 
several custom plugins and multiple SolrClouds deployed, we need to make it 
easy to both consume the official plugins, 3rd party plugins and also to setup 
their own company-internal repo (File share, HTTPs site, Artifactory etc) where 
these plugins can be self hosted.

The PF4J based implementation of SOLR-10665 has you covered for all of these 
([https://www.slideshare.net/janhoy/solrs-missing-plugin-ecosystem/44]):
 !repos.png|width=800!

> 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
>         Attachments: plugin-usage.png, repos.png
>
>
> 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.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