Aliases can already point to multiple collections, have you just tried that?
I'm not totally sure what the behavior would be, but nothing you've written indicates you tried so I thought I'd point it out. It's not clear to me how useful this is though, or what failure messages are returned. Or how you figure out which collection failed. Or how you'd take remedial action. Best, Erick Erick On Thu, Nov 9, 2017 at 10:09 AM, S G <sg.online.em...@gmail.com> wrote: > Hi, > > We have a use-case to re-create a solr-collection by re-ingesting > everything but not tolerate a downtime while that is happening. > > We are using collection alias feature to point to the new collection when > it has been re-ingested fully. > > However, re-ingestion takes several hours to complete and during that time, > the customer has to write to both the collections - previous collection and > the one being bootstrapped. > This dual-write is harder to do from the client side (because client needs > to have a retry logic to ensure any update does not succeed in one > collection and fails in another - consistency problem) and it would be a > real welcome addition if collection aliasing can support this. > > Proposal: > If can enhance the write alias to point to multiple collections such that > any update to the alias is written to all the collections it points to, it > would help the client to avoid dual writes and also issue just a single > http call from the client instead of multiple. It would also reduce the > retry logic inside the client code used to keep the collections consistent. > > > Thanks > SG
