Hi Erick, 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? Regards, Edwin On 5 June 2015 at 12:08, Erick Erickson <erickerick...@gmail.com> wrote: > In a word, no. Why do you change the collection name? If you're doing > some sort of switching the collection, consider collection aliasing. > > Best, > Erick > > On Thu, Jun 4, 2015 at 8:53 PM, Zheng Lin Edwin Yeo > <edwinye...@gmail.com> wrote: > > Hi, > > > > Would like to check, does all the collections in Solr have an ID that is > > stored internally which we can reference to? > > > > Currently I believe we are using the name of the collection when we are > > querying to the collection, and this can be modified as and when is > > required. Whenever this is changed, it will cause problem with my program > > as the old collection name doesn't exists anymore. > > > > So would like to know, does Solr creates an unique ID when a collection > is > > created, and this ID shouldn't change even if the collection name is > > changed? > > > > I'm using Solr 5.1 > > > > > > Regards, > > Edwin >
