[
https://issues.apache.org/jira/browse/SOLR-11099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16090708#comment-16090708
]
Hoss Man commented on SOLR-11099:
---------------------------------
i'm leary of new APIs and new lifecycles for new plugins -- we've seen how much
of a headache that can be in the past, and it would be particularly more so for
something that operates outside of the existing collection framework.
Considering that:
* the existing internal APIs available to request handlers already give custom
code the power to go find lists of collections, pull data from zk, executing
collection API level commands, etc....
* the existing request dispatcher logic is already capable of ensuring requests
for a collection are routed to a node hosting a replica of that collection
... it seems "good enough" to tell people in these very special cases that they
can create an "empty" collection and put their custom non-core/non-collection
specific logic there.
If nothing else: perhaps we just give people syntactic sugar for
registering/querying requestHandlers on the {{.system}} collection?
> Provide a mechanism to add non-core level handlers
> --------------------------------------------------
>
> Key: SOLR-11099
> URL: https://issues.apache.org/jira/browse/SOLR-11099
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Anshum Gupta
>
> As of now, only collection specific handlers can be added to Solr. There is
> no way to add handlers that need to manage the cluster, instead of the
> collection/shard. Adding a hook that allows users to write custom handlers at
> admin/cluster level, which are initialized at core container level would be
> good.
> The configuration for the same could be a part of either the properties file,
> or a separate file.
> Addition/modification or the same could be done using the config APIs.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
