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

Ishan Chattopadhyaya commented on SOLR-14599:
---------------------------------------------

bq. Editing a configSet is familiar and I think more realistic for most 
scenarios.
I think it will be a minority of such users.

It is important to discourage hand editing as much as possible. Just because we 
consider hand editing of configsets to be "expert" features, the experts have 
really not helped the adoption of the config APIs or have done anything to 
drive up its adoption or even to improve it to add support to have it as 
preferred option. It is unfortunate. Under such cirumstances, it might be 
better for the health of the project even to make life difficult for such 
experts.

> Introduce cluster level plugins through package manager
> -------------------------------------------------------
>
>                 Key: SOLR-14599
>                 URL: https://issues.apache.org/jira/browse/SOLR-14599
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Package Manager
>            Reporter: Ishan Chattopadhyaya
>            Assignee: Ishan Chattopadhyaya
>            Priority: Blocker
>             Fix For: 8.6
>
>         Attachments: SOLR-14599.patch
>
>          Time Spent: 1h 40m
>  Remaining Estimate: 0h
>
> SOLR-14404 made it possible to write request handlers that are registered at 
> core container level. This makes it possible for packages to have two types 
> of plugins:
> # Collection level
> # Cluster level
> This issue intends to introduce the latter via package manager. The manifest 
> for a package will now specify the type of the plugin. Such plugins can be 
> deployed directly without specifying a collection.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to