[
https://issues.apache.org/jira/browse/SOLR-6122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17879670#comment-17879670
]
David Smiley commented on SOLR-6122:
------------------------------------
My comment on https://github.com/apache/solr/pull/76 is purely an
implementation detail to avoid code duplication within SolrCloud. I could
elaborate on that but would prefer to create a JIRA issue on such a
refactoring. This issue here is not that.
On HTTP API harmony, we should look at this mostly from a V2 API standpoint,
which is undergoing change throughout the 9x release. The paint is wet; we can
change anything. See this [Google
Sheet|https://cwiki.apache.org/confluence/display/SOLR/SIP-16%3A+Polish+and+Prepare+v2+APIs+for+v1+Deprecation]
(linked from
[SIP-16|https://cwiki.apache.org/confluence/display/SOLR/SIP-16%3A+Polish+and+Prepare+v2+APIs+for+v1+Deprecation]).
CC [~gerlowskija]
> API to cancel an already submitted/running Collections API call
> ---------------------------------------------------------------
>
> Key: SOLR-6122
> URL: https://issues.apache.org/jira/browse/SOLR-6122
> Project: Solr
> Issue Type: Wish
> Components: SolrCloud
> Reporter: Anshum Gupta
> Priority: Major
>
> Right now we can trigger a long running task with no way to cancel it
> cleanly.
> We should have an API that interrupts the already running/submitted
> collections API call.
--
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
