Can't remap index alias pointing to read-only index

[outoftime]

See reduction (download):

curl -XDELETE http://localhost:9200/test1?pretty=true
echo ''
curl -XDELETE http://localhost:9200/test2?pretty=true
echo ''
curl -XPUT http://localhost:9200/test1?pretty=true -d '{}'
echo ''
curl -XPOST http://localhost:9200/_aliases?pretty=true -d '{"actions":[{"add":{"index":"test1","alias":"test"}}]}'
echo ''
curl -XPUT http://localhost:9200/test2?pretty=true -d '{}'
echo ''
curl -XPUT http://localhost:9200/test1/_settings?pretty=true -d '{"index":{"blocks":{"read_only":true}}}'
echo ''
curl -XPOST http://localhost:9200/_aliases?pretty=true -d '{"actions":[{"remove":{"index":"test1","alias":"test"}},{"add":{"index":"test2","alias":"test"}}]}'
echo ''

[kimchy]

Mmm, the problem here is that read_only was defined as not being allowed to "write" or do "metadata" changes to the index. Adding an alias constitutes metadata change... . It makes sense (though it could have easily been defined the to only disallow writes), and I am reluctant to change it now.

We can potentially add another option, like disable writes, but it feels like its going to be confusion. Not sure what the best answer for this is currently...

[outoftime]

Gotcha. I also noticed that doing e.g. a DELETE / fails if any of your indexes are read-only. This makes sense given your definition of "readonly", but for what it's worth, I think a "disable writes" would be much more useful than the read-only functionality as currently defined...

[kimchy]

Opened #1771, which will resolve this one.