[
https://issues.apache.org/jira/browse/SOLR-13996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17045931#comment-17045931
]
David Smiley commented on SOLR-13996:
-------------------------------------
IMO we should use the word "Standalone" for standalone solr and not the word
"Legacy", even if we imagine one day perhaps it might not be possible anymore.
We use this word Standalone already for the distinction -- the "Standalone"
subclass of ConfigSetService, for example, and SolrStandaloneScraper in the
prometheus contrib. Of course "Legacy" appears in many class names but it
merely means an old/deprecated way of doing something, not of Solr's standalone
mode specifically.
> Refactor HttpShardHandler#prepDistributed() into smaller pieces
> ---------------------------------------------------------------
>
> Key: SOLR-13996
> URL: https://issues.apache.org/jira/browse/SOLR-13996
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Assignee: Shalin Shekhar Mangar
> Priority: Major
> Attachments: SOLR-13996.patch, SOLR-13996.patch
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> Currently, it is very hard to understand all the various things being done in
> HttpShardHandler. I'm starting with refactoring the prepDistributed() method
> to make it easier to grasp. It has standalone and cloud code intertwined, and
> wanted to cleanly separate them out. Later, we can even have two separate
> method (for standalone and cloud, each).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
