lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrzej Bialecki (JIRA)" <>
Subject [jira] [Commented] (SOLR-13407) Reject updates sent to non-routed multi collection aliases
Date Wed, 17 Apr 2019 15:39:00 GMT


Andrzej Bialecki  commented on SOLR-13407:

Here's a patch that implements this change:
 * aliases need to be checked whether they refer to multiple collections but also also whether
they are routed or non-routed. Since this happens both in {{BaseCloudSolrClient}} and in {{HttpSolrCall}}
the only common interface to use was {{ClusterStateProvider}} so this patch extends it to
allow access to alias properties.
 * added convenience methods for checking whether an alias is routed.
 * a few other changes to try and minimize object allocations when expanding aliases.

> Reject updates sent to non-routed multi collection aliases
> ----------------------------------------------------------
>                 Key: SOLR-13407
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: Andrzej Bialecki 
>            Priority: Major
>             Fix For: 8.1, master (9.0)
>         Attachments: SOLR-13407.patch
> Spin-off from SOLR-13262.
> Currently Solr uses a convention that updates sent to multi-collection aliases are applied
only to the first collection on the list, which is nonintuitive and may hide bugs or accidental
configuration changes made either in Solr or in client applications.
> This issue proposes to reject all such updates with an error.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message