You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Andrzej Bialecki (JIRA)" <ji...@apache.org> on 2019/04/18 15:07:00 UTC
[jira] [Resolved] (SOLR-13407) Reject updates sent to non-routed
multi collection aliases
[ https://issues.apache.org/jira/browse/SOLR-13407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrzej Bialecki resolved SOLR-13407.
--------------------------------------
Resolution: Fixed
Assignee: Andrzej Bialecki
I added also a bit of documentation to {{aliases.adoc}} and to the Upgrade section in CHANGES.
> Reject updates sent to non-routed multi collection aliases
> ----------------------------------------------------------
>
> Key: SOLR-13407
> URL: https://issues.apache.org/jira/browse/SOLR-13407
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Andrzej Bialecki
> Assignee: 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org