Re: CREATEALIAS to non-existing collections

: > We currently support requests to CREATEALIAS to collections that don’t : > exist. Requests to this alias later result in 404s. If the target : > collection is later created, requests to the alias will begin to work. I’m : > wondering if someone is relying on this behavior, or

Re: CREATEALIAS to non-existing collections

I’d prefer it if the alias was required to be removed, or pointed elsewhere, before the collection could be deleted. As a best practice, I encourage all SolrCloud users to configure an alias to each collection, and use only the alias in their clients. This allows atomic switching between

Re: CREATEALIAS to non-existing collections

> On Dec 9, 2016, at 1:12 PM, Anshum Gupta wrote: > > On a similar note, I think we should also be clearing out the aliases when > we DELETE a collection. This seems problematic since an alias can point to several collections. Maybe the point is that the deleted

Re: CREATEALIAS to non-existing collections

I think that might have just been an oversight. We shouldn't allow creation of an alias for non-existent collections. On a similar note, I think we should also be clearing out the aliases when we DELETE a collection. -Anshum On Fri, Dec 9, 2016 at 12:57 PM Tomás Fernández Löbbe

CREATEALIAS to non-existing collections

We currently support requests to CREATEALIAS to collections that don’t exist. Requests to this alias later result in 404s. If the target collection is later created, requests to the alias will begin to work. I’m wondering if someone is relying on this behavior, or if we should validate the