Rafal Kuc is a team leader and software developer. Right now he is a software architect and Solr and Lucene specialist. Mainly focused on Java, but open on every tool and programming language that will make the achievement of his goal easier and faster. Rafal is also one of the founders of solr.pl site where he tries to share his knowledge and help people with their problems. Rafał is a DZone MVB and is not an employee of DZone and has posted 75 posts at DZone. You can read more from them at their website. View Full User Profile

Lucene Eurocon 2011: Day Two

11.14.2011
| 4191 views |
  • submit to reddit

In the previous entry, we tried to cover what we saw at the first day of Lucene Eurocon 2011 conference. However, from our point of view, the second day was the more important one, due to the fact that this was the day we had our talk. But let’s start from the beginning.

Keynote (Realtime Search at Twitter, Michael Busch)

Day two began with one of the better, in my opinion, talks during Lucene Eurocon 2011. Michael Busch, during his presentation titled “Realtime Search at Twitter” (slides, video) showed us what the Twitter team to handle real-time search based on Lucene, so that the whole system was able to handle the daily traffic of Twitter. The presentation consisted of a very large amount of technical details, details that were explained in details. Conference participants, in addition to the information about Lucene, also got a brief lesson of Java multithreaded programming :)

What will come (Lucene Today, Tomorrow & Beyond, Simon Willnauer)

The conference was divided into three parallel sessions, and we chose the presentation titled “Lucene Today, Tomorrow & Beyond” (slides, video) , led by Simon Willnauer. The presentation focused on what Lucene is not capable of at this time, and what it may be capable of in the future (for example, in version 5). Simon began by presenting the history of Lucene, the people involved in the development of the project and the companies they work for. Then we found out what users can expect from Lucene (in terms of functionalities), when version 4.0 is officially released. During the talk, Simon also talked about that the role of positions of tokens in the token stream, incremental updates and JIT. At the end we were shown a part of his vision of Lucene and Solr as a modular projects.

A thing about explain in Solr (Understanding and Visualising Solr ‘explain’ Information, Rafał Kuć)

For personal reasons and because I wanted to prepare for the talk I desided to skip one of the talks. And after the lunch, my talk began. The presentation titled “Understanding and Visualising Solr ‘explain’ Information” (slides) was divided into two parts – first, the theory regarding the information returned by Apache Solr and the second – what we have done for http://explain.solr.pl. Let me not to comment on my own presentation, and focus on what I felt after it. Unfortunately, I was not pleased after the talk, stress ate me alive – I didn’t say all I wanted to say, I rushed and not explained what I wanted to. But now, after having some experience I can promise one thing – next time will be better, much better. I am pleased with the positive reception of the talk and the topic itself.

Randomized tests (Randomized Continous Testing: Solr & Lucene Use Case, Dawid Weiss)

After a short rest we went to listen as David Weiss talks about tests using a random factor during the talk titled “Randomized Continous Testing: Solr & Lucene Use Case” (slides). If you are interested about the automated testing (and you should be) I definitely recommend the slides, as well as video as soon as it’ll be available. David started with the theory about where you can add a random factor to the tests (of course everything in the context of Lucene and Solr). Then we got a good deal of technical information on how to implement a randomized test (with examples of course). There were also information on how to test multi-threading.

How to test your search engine (Better Search Engine Testing, Eric Pugh)

Staying in the topic of testing, we decided to go to the last talk during Lucene Eurocon 2011 titled “Better Search Engine Testing” (slides), led by Eric Pugh.

Commiter panel

The last attraction in the Lucene Eurocon 2011 was the “Commiter panel” – the meeting of conference participants and the people that develop Apache Lucene and Solr every day. After brief introductions, there was a series of questions and answers. If you are interested how the meeting went, you will have to wait for the video material. Another interesting presentation, at least from my point of view. Eric started from the fact that search, and particularly good search is increasingly important in today’s world. What’s more, data storage is cheap, but data management is by no means cheap, and therefore the role of search engines will increase. Eric then turned our attention to the problem of testing the search engines, what should be tested and how we can automatically test the search engines. It’s hard to write a summary of that talk, due to the large amount of information that Eric had given.

Other presentations

I would also like to invite persons interested in presentations other than those discussed in this and the previous entry to the following sites:

To sum up

From my point of view, Lucene Eurocon 2011 conference was much better organized than Lucene Eurocon 2010, even considering the fact that the Lucene Eurocon 2010 conference was very good. You could see that the organizers gained experience :) The talks at the conference were miscellaneous – there were strictly technical subjects and those that focused on the user. Because of the three parallel sessions, it was impossible not to find the presentation for yourself – the organizers deserve thanks and congratulations, they did a very good job. I hope that we will meet most of this year’s participants in the Lucene Eurocon 2012 ;)


Source:  http://solr.pl/en/2011/11/14/lucene-eurocon-2011-day-two/
Published at DZone with permission of Rafał Kuć, author and DZone MVB.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)