So, all in all, is there anybody who can write down just main steps of Solr(including parsing, stemming etc.)?
2013/4/2 Furkan KAMACI <furkankam...@gmail.com> > I think about myself as an example. I have started to make research about > Solr just for some weeks. I have learned Solr and its related projects. My > next step writing down the main steps Solr. We have separated learning > curve of Solr into two main categories. > First one is who are using it as out of the box components. Second one is > developer side. > > Actually developer side branches into two way. > > First one is general steps of it. i.e. document comes into Solr (i.e. > crawled data of Nutch). which analyzing processes are going to done > (stamming, hamming etc.), what will be doing after parsing step by step. > When a search query happens what happens step by step, at which step scores > are calculated so on so forth. > Second one is more code specific i.e. which handlers takes into account > data that will going to be indexed(no need the explain every handler at > this step) . Which are the analyzer, tokenizer classes and what are the > flow between them. How response handlers works and what are they. > > Also explaining about cloud side is other work. > > Some of explanations are currently presents at wiki (but some of them are > at very deep places at wiki and it is not easy to find the parent topic of > it, maybe starting wiki from a top age and branching all other topics as > possible as from it could be better) > > If we could show the big picture, and beside of it the smaller pictures > within it, it would be great (if you know the main parts it will be easy to > go deep into the code i.e. you don't need to explain every handler, if you > show the way to the developer he/she could debug and find the needs) > > When I think about myself as an example, I have to write down the steps of > Solr a bit detail even I read many pages at wiki and a book about it, I > see that it is not easy even writing down the big picture of developer side. > > > 2013/4/2 Alexandre Rafalovitch <arafa...@gmail.com> > >> Yago, >> >> My point - perhaps lost in too much text - was that Solr is presented - >> and >> can function - as a black-box. Which makes it different from more >> traditional open-source project. So, the stage-2 happens exactly when the >> non-programmers have to cross the boundary from the black-box into >> code-first approach and the hand-off is not particularly smooth. Or even >> when - say - php or .Net programmer tries to get beyond the basic >> operations their client library and has the understand the server-side >> aspects of Solr. >> >> Regards, >> Alex. >> >> On Tue, Apr 2, 2013 at 1:19 PM, Yago Riveiro <yago.rive...@gmail.com> >> wrote: >> >> > Alexandre, >> > >> > You describe the normal path when a beginner try to use a source of code >> > that doesn't understand, black-box, reading code, hacking, ok now I know >> > 10% of the project, with lucky :p. >> > >> >> >> Personal blog: http://blog.outerthoughts.com/ >> LinkedIn: http://www.linkedin.com/in/alexandrerafalovitch >> - Time is the quality of nature that keeps events from happening all at >> once. Lately, it doesn't seem to be working. (Anonymous - via GTD book) >> > >
