dsmiley commented on PR #2363: URL: https://github.com/apache/solr/pull/2363#issuecomment-2556137265
@markrmiller , thinking back to your feedback, I have an idea of a solution in several steps: (A) In https://issues.apache.org/jira/browse/SOLR-17601 I propose using HTTP response headers to inform the client of the state version of a collection that the client is interacting with. Imagine if collection admin commands participated in this (not just handlers on the core) like create collection. Thus when CREATE returns, the header indicates the version of the final created state. Let's also assume waitForState=true[1]. (B) Even though the CloudSolrClient's cache[2] wouldn't yet have a DocCollection, let's imagine an enhancement to this cache in which it can hold a cache entry without a DocCollection but with a version to indicate we now want this version (or greater). At least for HTTP ClusterStateProvider, it will fetch the CLUSTERSTATE from Solr via HTTP. What's new -- imagine it adds the \_stateVer\_ parameter. (C) HttpSolrCall will see the \_stateVer\_ param. If it's DocCollection isn't as high as this version, it forces an update. I think this part works as-is but perhaps some work may be needed. [1] why the heck is waitForState not true by default? [2] the CSC's cache should move to ClusterStateProvider -- https://issues.apache.org/jira/browse/SOLR-17604 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
