Yonik, thanks for sharing deeper details about how SolrCloud is going to work. Do you plan to release any wiki-updates about the small details, so that other developers are able to get in touch with what you've already done there?
I think small guides and the mentioning of class-names and their relationships and/or lifecycles are good startpoints that do not need much time to write them down (take "How to write distributed SearchComponents" as an example). Kind regards, Em Am 24.02.2012 15:18, schrieb Yonik Seeley: > On Fri, Feb 24, 2012 at 8:59 AM, Per Steffensen <st...@designware.dk> wrote: >> We might make it "outside" Solr/Lucene but I >> hope to be able to convince my ProductOwner to make it as a Solr-feature >> contributing it back - especiallly if the Solr community agrees that it >> would be a nice and commonly usable feature. > > Our current distributed indexing (solr cloud) design explicitly took > optimistic concurrency into account, and it's been on my todo list. > It should actually be pretty easy - we have all the plumbing in place > now that we already use for distributed indexing. > For example, versioning is already used to handle reorders of updates > when a leader forwards updates to replicas (and an older update to a > document is simply dropped). > > If you'd like to help out, the starting point where versioning is > handled is in DistributedUpdateProcessor (which is now a default > processor and also works in non-distrib mode). > > -Yonik > lucidimagination.com >
