[
https://issues.apache.org/jira/browse/SOLR-13724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16918122#comment-16918122
]
Jason Gerlowski commented on SOLR-13724:
----------------------------------------
Here's a quick way to reproduce the behavior:
{code}
➜ solr git:(fcbe46c28ce) ✗ bin/solr start -c
Waiting up to 180 seconds to see Solr running on port 8983 [\]
Started Solr server on port 8983 (pid=20921). Happy searching!
➜ solr git:(fcbe46c28ce) ✗ bin/solr create -c foo
Created collection 'foo' with 1 shard(s), 1 replica(s) with config-set 'foo'
➜ solr git:(fcbe46c28ce) ✗ bin/solr create -c bar
Created collection 'bar' with 1 shard(s), 1 replica(s) with config-set 'bar'
➜ solr git:(fcbe46c28ce) ✗ curl -ilk -X GET
"http://localhost:8983/solr/admin/collections?action=CREATEALIAS&name=my_alias&collections=foo,bar";
HTTP/1.1 200 OK
Content-Type: application/json;charset=utf-8
Content-Length: 57
{
"responseHeader":{
"status":0,
"QTime":128}}
➜ solr git:(fcbe46c28ce) ✗ curl -ilk -X POST -H "Content-type:
application/json" "http://localhost:8983/solr/my_alias/update?commit=true"; -d
'[{"id": "asdf", "val_i": 4}]'
HTTP/1.1 200 OK
Content-Type: text/plain;charset=utf-8
Content-Length: 69
{
"responseHeader":{
"rf":1,
"status":0,
"QTime":373}}
{code}
> Reject v1 API updates for (non-routed) multi-collection aliases
> ---------------------------------------------------------------
>
> Key: SOLR-13724
> URL: https://issues.apache.org/jira/browse/SOLR-13724
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 8.1, master (9.0)
> Reporter: Jason Gerlowski
> Priority: Major
>
> The intent of SOLR-13407 was to block all updates on aliases that represent
> multiple collections. Currently, this works for deletes, commits, and
> optimize requests. Users get a message like: {{Update request to non-routed
> multi-collection alias not supported}}.
> But currently we still allow document adds/updates to go through.
> We should either close this last hole, so _no_ update requests are allowed,
> or document it so the behavior clearer.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
