Description
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.
Attachments
Attachments
Issue Links
- is related to
-
SOLR-13262 Implement collection RENAME command
- Closed
- relates to
-
SOLR-13724 Reject v1 API updates for (non-routed) multi-collection aliases
- Open