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

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

I started a thread a week back about this on the dev@ mailing list 
("Deprecation/Backcompat for Internal+Undocumented APIs") and got two +1's for 
removing the API without concern for backcompat, with no one disagreeing.  I'll 
take that as lazy consensus and create a PR removing this API.

It'd be awesome if we had our backcompat/deprecation policy written up 
somewhere that covered the exceptions and edge cases like this - maybe in our 
dev-docs?  Maybe I'll consider that as an additional follow-up here.

> 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-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to