[
https://issues.apache.org/jira/browse/SOLR-13662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16935145#comment-16935145
]
Jan Høydahl commented on SOLR-13662:
------------------------------------
Repo handling is already implemented in SOLR-10665, and here is the CLI syntax:
!plugin-cli.png|width=800!
Of course, the POC does not deal with multiple simultaneous versions of same
plugin, but that is not hard to extend.
You should not be required to know the version number of the plugin when
installing, like in your proposal in this issue. Instead, the plugin installer
compares your Solr version with the "requires" expression in the repository
manifest and resolves the newest plugin version that is compatible with your
system. So say you still run Solr 7.5.1 then the package manager will give you
DIH v7.5.1 when you do {{solr install dih}}
Also I don't think users should need to specify what collections the plugin is
available for. We should optimize for the 80% usecase, i.e. make the latest
version of the plugin available for ALL collections. Instead of deciding this
install-time I proposed in
[https://www.slideshare.net/janhoy/solrs-missing-plugin-ecosystem/47] to define
a {{<dependency>my-plugin</dependency>}} tag in solrconfig.xml. That *could* be
extended to include a specific version too, but in my mind, what version(s) of
a certain plugin to install is more dependent on the actual version of Solr you
run than it is of the features you need to use in a given collection.
> Package manager CLI
> -------------------
>
> Key: SOLR-13662
> URL: https://issues.apache.org/jira/browse/SOLR-13662
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Noble Paul
> Assignee: Ishan Chattopadhyaya
> Priority: Major
> Attachments: plugin-cli.png
>
>
> example scripts
> {code}
> #add a repo to your Solr cluster. This adds the public key of the repo to our
> Solr ZK
> # also store the file in /package-repo in ZK
> bin/solr plugin add-repo <http:url-of-repo>
> # searches all the registered repos for the pakage 'solr-highlighting" and
> version :0.1 and add
> # the package to solr cluster. After it's done thes component will be added
> to collections, coll1,coll2,coll3
> bin/solr plugin install solr-highlighting:0.1 -c coll1,coll2,coll3
> # deploy an already installed package to an existing set of collections
> bin/solr plugin deploy solr-highlighting -c coll1,coll2
> # update an existing package solr-highlighting to , version '0.2'. This
> automatically
> #updates all the collections using this package
> bin/solr plugin update solr-highlighting:0.2
> # search and list all the registered repos for a component which has a string
> 'highlight' in description
> bin/solr plugin search “highlight”
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
