We're using aliases to control visibility of collections we rebuild from scratch nightly. It works pretty well. If you run CREATEALIAS again, it'll switch to a new one, not augment the old one.
If for some reason, you want to bridge more than one collection, you can add more than one collection to the alias at creation time, but then it becomes read-only. Michael Della Bitta ------------------------------------------------ Appinions 18 East 41st Street, 2nd Floor New York, NY 10017-6271 www.appinions.com Where Influence Isn’t a Game On Wed, Apr 24, 2013 at 12:26 PM, Jon Strayer <j...@strayer.org> wrote: > We are using a Solr collection to serve auto complete suggestions. We'd > like for the update to be without any noticeable delay for the users. > > I've been looking at adding new cores, loading them with the new data and > then swapping them with the current ones, but but I don't see how that > would work in a cloud installation. It seems that when I create a new core > it is part of the collection and the old data will start replicating to it. > Is that correct? > > I've also looked at standing up a new collection and then adding an alias > for it, but that's not well documented. If the alias already exists and I > add to to another collection is it removed from the first collection? > > I'm open to any suggestions. > > -- > To *know* is one thing, and to know for certain *that* we know is another. > --William James
