[jira] [Resolved] (SOLR-15157) Refactor: separate Collection API commands from Overseer and message handling logic

["David Smiley (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SOLR-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

David Smiley resolved SOLR-15157.
---------------------------------
    Fix Version/s: 9.0
       Resolution: Fixed

> Refactor: separate Collection API commands from Overseer and message handling logic
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-15157
>                 URL: https://issues.apache.org/jira/browse/SOLR-15157
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrCloud
>    Affects Versions: 9.0
>            Reporter: Ilan Ginzburg
>            Assignee: Ilan Ginzburg
>            Priority: Major
>             Fix For: 9.0
>
>          Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> Collection API command execution happens in Overseer. The code dealing with Overseer specific abstractions (Collection API queue management, executing threads etc) is mixed with code implementing the Collection API commands.
> The goal of this ticket is refactoring the Collection API code to abstract anything that is related to how the Overseer executes the commands, in order to enable a future ticket (SOLR-15146) to introduce a distributed execution mode for the Collection API (and keeping the changes limited).
> This ticket does not introduce any changes regarding how the Collection API commands run in the Overseer. It is only refactoring the call chains to allow a future separation.



--
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