You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@solr.apache.org by "Jason Gerlowski (Jira)" <ji...@apache.org> on 2022/10/12 18:56:00 UTC

[jira] [Commented] (SOLR-16459) Deprecate and remove /admin/cores?action=INVOKE

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

Jason Gerlowski commented on SOLR-16459:
----------------------------------------

My main question in removing this functionality is: does Solr's standard backcompat and deprecation policy apply to undocumented, internal APIs such as /admin/cores?action=INVOKE?

Should I leave it in 9.x with a deprecation warning, or is it reasonable to remove it altogether in the 9.x line? 

> Deprecate and remove /admin/cores?action=INVOKE
> -----------------------------------------------
>
>                 Key: SOLR-16459
>                 URL: https://issues.apache.org/jira/browse/SOLR-16459
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 8.11.2, 9.1
>            Reporter: Jason Gerlowski
>            Priority: Major
>
> SOLR-6220 added an "INVOKE" action to CoreAdminHandler as a means to implement the old form of rule-based replica placement.  The API itself iterates over an arbitrary number of class names, instantiating each one and calling its "invoke" method via reflection.
> Now that the old form of rule-based replica placement was removed in 9, nothing uses this API "action" anymore and it should be removed: both for complexity/maintenance reasons, and for potential security issues.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@solr.apache.org
For additional commands, e-mail: issues-help@solr.apache.org