[ https://issues.apache.org/jira/browse/SOLR-11507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16235132#comment-16235132 ]
David Smiley commented on SOLR-11507: ------------------------------------- Thanks for your input [~gerlowskija]. I didn't know about SOLR-10469. I should split this patch in two -- the SOLR-10469 part and the randomization part here. bq. Most of the other setters have "move to setter" issues filed. IMO we don't need a JIRA issues for each setter; it's okay to lump them all into a common theme! Creating many JIRA issues creates an administrative burden with dubious if any benefits. > simplify and extend SolrTestCaseJ4.CloudSolrClientBuilder randomisation > ----------------------------------------------------------------------- > > Key: SOLR-11507 > URL: https://issues.apache.org/jira/browse/SOLR-11507 > Project: Solr > Issue Type: Test > Reporter: Christine Poerschke > Priority: Minor > Attachments: SOLR-11507.patch, SOLR-11507.patch > > > [~dsmiley] wrote in SOLR-9090: > bq. [~cpoerschke] I'm looking at {{SolrTestCaseJ4.CloudSolrClientBuilder}}. > Instead of the somewhat complicated tracking using configuredDUTflag, > couldn't you simply remove all that stuff and just modify the builder's > constructor to randomize the settings? > bq. Furthermore, shouldn't {{shardLeadersOnly}} be randomized as well? > This ticket is to follow-up on that suggestion since SOLR-9090 is already > closed. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org