That's why we are trying to get the user to change something else instead of the collection name. The collection alias sounds like a good option.
Is there a way to list out all the alias names, or the only way is to reference it at aliases.json file under the Cloud section in the Admin UI? As when I use the /admin/collections?action=LIST, it list the collection names only, and I'm using this to populate the collections on the UI dynamically. If the user is using the alias name, there's no need for them to know the actual collection name. So I'm trying to find a way is there a way to list out all the alias name. Regards, Edwin On 5 June 2015 at 14:10, Shawn Heisey <apa...@elyograg.org> wrote: > On 6/4/2015 11:39 PM, Zheng Lin Edwin Yeo wrote: > > The reason is we want to allow flexibility to change the collection name > > based on the needs of the users. > > > > For the collection aliasing, does this mean that the user will reference > > the collection by the alias name instead of the collection name, but at > the > > backend we will still reference by the collection name? Whenever the user > > wants to change the name, they'll just change the alias name, and leave > the > > collection name intact? > > The users can change the collection name? That sounds like a recipe for > disaster. > > Collection aliases are a way for an admin to do index swapping in > SolrCloud so that new indexes can be built and then swapped with the old > index. You build a collection named something like foo20150605 and then > set up an alias named "foo" that points to that collection. Your > program doesn't need to know about the real collection name, the alias > redirects all activity from the well-known name to the actual > collection, and that mapping can change anytime it needs to. > > Thanks, > Shawn > >
