[ https://issues.apache.org/jira/browse/SOLR-4043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13553449#comment-13553449 ]
Mark Miller commented on SOLR-4043: ----------------------------------- I suppose you could look at it either way - but the way it currently works was intentional given time and priorities. I look at this as an improvement on that - it was always planned. It will be in 4.2 - but I don't think I'll have time to do a proper vetting for 4.1. > Add ability to get success/failure responses from Collections API. > ------------------------------------------------------------------ > > Key: SOLR-4043 > URL: https://issues.apache.org/jira/browse/SOLR-4043 > Project: Solr > Issue Type: Improvement > Components: SolrCloud > Affects Versions: 4.0-ALPHA, 4.0-BETA, 4.0 > Environment: Solr cloud cluster > Reporter: Raintung Li > Assignee: Mark Miller > Fix For: 4.1, 5.0 > > Attachments: patch-4043.txt, SOLR-4043_brach4.x.txt, SOLR-4043.patch > > > The create/delete/reload collections are asynchronous process, the client > can't get the right response, only make sure the information have been saved > into the OverseerCollectionQueue. The client will get the response directly > that don't wait the result of behavior(create/delete/reload collection) > whatever successful. > The easy solution is client wait until the asynchronous process success, the > create/delete/reload collection thread will save the response into > OverseerCollectionQueue, then notify client to get the response. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org