On 23/07/14 17:13, Erick Erickson wrote:
Per:
Given that you said that the field redefinition also includes routing
info....
Exactly. It would probably be much faster to make sure that the new
collection have the same number of shards on each Solr-machine and that
the routing-ranges are identical and then to a local 1-1 copy on
shard-level. But it just will not end up correctly wrt routing, because
we also need to change our ids while copying from old to new collections.
I don't see
any other way than re-indexing each collection. That said, could you use the
collection aliasing and do one collection at a time?
We will definitely do one collection at the time. Whether we will use
aliasing or do something else to achieve create-new-twin-collection ->
copy-from-old-collection-to-new-twin-collection ->
delete-old-collection-and-let-new-twin-collection-take-its-place I do
not know yet. But that is details, we will definitely be able to manage.
Best,
Erick
