chatman commented on pull request #1684: URL: https://github.com/apache/lucene-solr/pull/1684#issuecomment-664046970
> There’s no direct mapping between work orders and collection API. I consider work orders the basic building blocs from which collection API actions can be built. Creating a collection (adding the data in ZK, checking for the config set etc) is different from adding a replica to an existing collection. Hence the two work orders. The “new collection” doesn’t add any replicas to the collection but prepares the system to accept adding replicas replicas for the collection. Obviously when adding a replica to an existing collection, that preparation work is not required. Why can't we have a single type of work order that requests for the preparation of n number of replicas (where n is 1 in case of ADDREPLICA and n is numShards*replicationFactor in case of CREATE)? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
