[
https://issues.apache.org/jira/browse/SOLR-12770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16743347#comment-16743347
]
ASF subversion and git services commented on SOLR-12770:
--------------------------------------------------------
Commit e9db95831b9db69fbc0bef499b0d3f41bc6448f1 in lucene-solr's branch
refs/heads/branch_8x from Tomas Eduardo Fernandez Lobbe
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=e9db958 ]
SOLR-12770: Make it possible to configure a host whitelist for distributed
search
> Make it possible to configure a shards whitelist for master/slave
> -----------------------------------------------------------------
>
> Key: SOLR-12770
> URL: https://issues.apache.org/jira/browse/SOLR-12770
> Project: Solr
> Issue Type: New Feature
> Security Level: Public(Default Security Level. Issues are Public)
> Components: search
> Reporter: Jan Høydahl
> Priority: Major
> Labels: masterSlave
>
> For legacy master/slave clusters, there is no Zookeeper to keep track of all
> the nodes and shards in the cluster. So users manage the 'shards' parameter
> manually for distributed search. This issue will add the option of
> configuring a list of what shards can be requested.
> Users will then get an explicit error response if the request includes a
> shard which is not in the preconfigured whitelist, e.g. due to a typo. I
> think all shards logic is handled by HttpShardHandler already so the logic
> should fit nicely in that one class, configured in {{solr.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
