[
https://issues.apache.org/jira/browse/SOLR-15157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331317#comment-17331317
]
David Smiley commented on SOLR-15157:
-------------------------------------
If you think it's done, then just move to "Resolved" state via the "Resolve
Issue" button. Choose main/9.0 version and no others. Don't further advance
from there to "Closed"; that occurs en-masse on releases.
On the other hand, if you think there are lingering test failures/issues, then
you could leave open for longer.
> 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: main (9.0)
> Reporter: Ilan Ginzburg
> Assignee: Ilan Ginzburg
> Priority: Major
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
