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

ASF subversion and git services commented on SOLR-10446:
--------------------------------------------------------

Commit 7eedb81c4274bf1b9ad4f3b2e3ef6ae1b816469e in lucene-solr's branch 
refs/heads/branch_6x from [~ichattopadhyaya]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=7eedb81 ]

SOLR-10447, SOLR-10447: LISTALIASES Collections API command; CloudSolrClient 
can be initialized using Solr URL

   SOLR-10447: Collections API now supports a LISTALIASES command to return a 
list of all collection aliases.

   SOLR-10446: CloudSolrClient can now be initialized using the base URL of a 
Solr instance instead of
    ZooKeeper hosts. This is possible through the use of newly introduced 
HttpClusterStateProvider.
    To fetch a list of collection aliases, this depends on LISTALIASES command, 
and hence this way of
    initializing CloudSolrClient would not work with older versions of Solr 
that doesn't support LISTALIASES.


> Http based ClusterStateProvider (CloudSolrClient needn't talk to ZooKeeper)
> ---------------------------------------------------------------------------
>
>                 Key: SOLR-10446
>                 URL: https://issues.apache.org/jira/browse/SOLR-10446
>             Project: Solr
>          Issue Type: Sub-task
>          Components: SolrJ
>            Reporter: Ishan Chattopadhyaya
>         Attachments: SOLR-10446.patch, SOLR-10446.patch, SOLR-10446.patch, 
> SOLR-10446.patch, SOLR-10446.patch, SOLR-10446.patch, SOLR-9057.patch
>
>
> An HTTP based ClusterStateProvider to remove the sole dependency of 
> CloudSolrClient on ZooKeeper, and hence provide an optional way for CSC to 
> access cluster state without requiring ZK.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to