A variation on #1 here - Use the same cluster, create a new collection, but use
the createNodeSet option to logically partition your cluster so no node has
both the old and new collection.
If your clients all reference a collection alias, instead of a collection name,
then all you need to do w
There are two options as I see it..
1. Do something like you describe and create a secondary index, index into
it, then switch... I personally would create a completely separate solr
cloud alongside my existing one vs new core in the same cloud as you might
see some negative impacts on GC caused b
Hi everyone,
In my environment, I have use cases where I need to fully re-index my
data. This happens because Solr's schema requires changes based on changes
made to my data source, the DB. For example, my DB schema may change so
that it now has a whole new set of field added or removed (on reco
