[
https://issues.apache.org/jira/browse/SOLR-12385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484420#comment-16484420
]
Steve Rowe commented on SOLR-12385:
-----------------------------------
Yonik commented about the need to fold SolrTestCaseHS into the standard
framework [on
SOLR-7214|https://issues.apache.org/jira/browse/SOLR-7214?focusedCommentId=14379043&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14379043]:
{quote}
We still need to handle SolrTestCaseHS as well (HS stands for HelioSearch).
Some of that class should prob just go back into SolrTestCaseJ4, but some of it
(the client stuff) might make sense somewhere else.
{quote}
> Tests extending SolrTestCaseHS should be cut over to SolrCloudTestCase, and
> unique SolrTestCaseHS functionality should be folded into the standard test
> infrastructure
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: SOLR-12385
> URL: https://issues.apache.org/jira/browse/SOLR-12385
> Project: Solr
> Issue Type: Task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Tests
> Reporter: Steve Rowe
> Priority: Minor
>
> SolrTestCaseHS is extended only by JSON facet and JSON request tests.
> SolrTestCaseHS was introduced with JSON faceting in SOLR-7214 (I believe "HS"
> is short for HelioSearch, where the functionality was originally developed).
> It appears to enable a primitive distributed functionality, with no
> ZooKeeper, allowing tight control of document distribution, like SolrCloud's
> implicit routing. Some JSON-specific handling stuff in there too, which I
> think could be relocated to JSONTestUtil.
> Alan Woodward and others did a bunch of test conversions to SolrCloudTestCase
> (e.g. SOLR-9132, SOLR-9110, SOLR-9065), but AFAICT never mentioned
> SolrTestCaseHS-based tests as a target.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
