In my experience, when trying to work on a large/new code base, fixing bugs is a great way to start.
You can see how pieces of the code work together and ask questions of other developers. They're excited to help you as you're fixing bugs and helping improve the system. On Sunday, October 5, 2014 8:44:05 AM UTC-7, ahmed jamal maaz wrote: > > Hi, > > I am a newbie to elasticsearch and lucene. I am going through its source > code. I like the general idea of search on Lucene. > > My Problem: > There is tons of code elasticsearch + lucene in the project. I am > requesting (curl url) and going through step by step (in debug mode). Are > there any recommendations and tips which can help me in increasing the pace > of this. This is taking too long. I don't have any issues, i will spend > time. But are there any parts which i should look first and then the > others. Such that i can learn complete and in a structured manner. > > Current State: > I have touch the bottom of insertion (creating new index) and general > querying. > > Thanks in advance. > > Obliged > Jamal > -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a65b10b4-7b5c-43b7-955f-a06aef82c0c9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
