The MIGRATE command is a synchronous operation and therefore keeping a large read timeout on the invocation is advised. The request may still timeout due to inherent limitations of the Collection APIs but that doesn’t necessarily mean that the operation has failed. Users should check logs, cluster state, source and target collections before invoking the operation again.
This command works only with collections having the compositeId router. The target collection must not receive any writes during the time the migrate command is running otherwise some writes may be lost. Please note that the migrate API does not perform any de-duplication on the documents so if the target collection contains documents with the same uniqueKey as the documents being migrated then the target collection will end up with duplicate documents. -- View this message in context: http://lucene.472066.n3.nabble.com/Some-clarification-needed-on-migrate-command-in-Collections-API-tp4165190p4165225.html Sent from the Solr - User mailing list archive at Nabble.com.
