Skip to content
Andrea Gazzarini edited this page Jun 29, 2018 · 2 revisions

For a better understanding of the overall process, we recommend to create first a project skeleton using the Maven Archetype. In order to have a quick taste about RRE, the target search platform is not relevant, so you can choose, among the available bindings (Apache Solr or Elasticsearch) the platform where you feel more confident.

The subsequent sections offer detailed information about what RRE expects in input. Instead the focus here, on this general section, is to highlight the overall process and its goals.

Let's say there's a search system you have to work with (i.e. configuration, tuning, implementation, fixes). Regardless it is a new or existing system, the development process necessarily passes through a set of iterations, where you change/remove/add something.

RRE answers to the following questions: how can I measure the improvement or the loss between a set of changes? How can I have a real-time view, at several levels of granularity, about the direction where the system is going?

The subsequent sections will drive you through the overall evaluation process. At the end you will have a full understanding about the RRE project structure, the evaluation process, the required input and the output.