[
https://issues.apache.org/jira/browse/SOLR-8323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15276961#comment-15276961
]
ASF GitHub Bot commented on SOLR-8323:
--------------------------------------
Github user romseygeek commented on the pull request:
https://github.com/apache/lucene-solr/pull/32#issuecomment-217978029
On further reflection, I've pulled the separate executor back out again. I
think the SolrZkClient's separate executor will work well enough, and for the
most part client code is going to be run inside a CloudSolrClient talking to
the cluster, not a Solr node's internal state reader. I've also removed the
CSC.registerCollectionWatcher() method, as that's really only for internal use,
leaving the waitForState() method as a convenience.
I'd like to commit this in the next couple of days. I think it will make a
big difference to a bunch of test improvements I want to make separately.
> Add CollectionWatcher API to ZkStateReader
> ------------------------------------------
>
> Key: SOLR-8323
> URL: https://issues.apache.org/jira/browse/SOLR-8323
> Project: Solr
> Issue Type: Improvement
> Affects Versions: 6.0
> Reporter: Alan Woodward
> Assignee: Alan Woodward
> Attachments: SOLR-8323.patch, SOLR-8323.patch, SOLR-8323.patch,
> SOLR-8323.patch
>
>
> An API to watch for changes to collection state would be a generally useful
> thing, both internally and for client use.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
