[ 
https://issues.apache.org/jira/browse/SOLR-9065?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272751#comment-15272751
 ] 

Joel Bernstein commented on SOLR-9065:
--------------------------------------

The following test cases were clearly under development at the time when this 
ticket was committed:

solr/solrj/src/test/org/apache/solr/client/solrj/io/graph/GraphExpressionTest.java
solr/solrj/src/test/org/apache/solr/client/solrj/io/graph/GraphTest.java
solr/solrj/src/test/org/apache/solr/client/solrj/io/sql/JdbcTest.java
solr/solrj/src/test/org/apache/solr/client/solrj/io/stream/JDBCStreamTest.java
solr/solrj/src/test/org/apache/solr/client/solrj/io/stream/StreamExpressionTest.java
solr/solrj/src/test/org/apache/solr/client/solrj/io/stream/StreamingTest.java

All that needed to be done was to notify the committers who maintain these 
tests and let them know a wholesale change was coming. Then there could have 
been a conversation about how to move forward without stepping on peoples work. 
Instead a patch went up and the next day it was committed. 



> Migrate solrj tests from AbstractDistribZkTestBase to SolrCloudTestCase
> -----------------------------------------------------------------------
>
>                 Key: SOLR-9065
>                 URL: https://issues.apache.org/jira/browse/SOLR-9065
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 6.1, master
>            Reporter: Alan Woodward
>            Assignee: Alan Woodward
>         Attachments: SOLR-9065.patch
>
>
> AbstractDistribZkTestBase sets up collections using the legacy core-based 
> system, and does a lot of comparing things against control collections that 
> the SolrJ tests really don't require.  We should migrate these tests to using 
> SolrCloudTestCase instead.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to