We are actually very close to doing what Shawn has suggested.
Emir has a good point about new collections failing on deletes/updates of
older documents which were not present in the new collection. But even if
this
feature can be implemented for an append-only log, it would make a good
feature IMO
This approach could work only if it is append only index. In case you have
updates/deletes, you have to process in order, otherwise you will get incorrect
results. I am thinking that is one of the reasons why it might not be supported
since not too useful.
Emir
--
Monitoring - Log Management -
On 11/9/2017 11:09 AM, S G wrote:
> 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
>
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
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
