Display Suite can override the way that Drupal's (and Apache solr's) default search results are being displayed. This will be useful if you wanted to include images or file attachments in search results.
Modify schema.xml so that it supports geo location values
WHAT/WHERE search (radius based) - instead of a single keyword based search
Content-type based filtration
Implementation of hook_apachesolr_index_document_build, hook_apachesolr_query_alter
I am not going through the steps for installing / connecting solr with drupal. A lot of articles are already available online.
Case
Typically for job/property search sites, where you have two text fields: WHAT and WHERE. I am using the apachesolr search pages for this implementation.
Example search:
WHAT: drupal architect
WHERE: Mumbai, Maharashtra, India
(basically, the 'where' is an autofill textbox - which gets data from YQL - and its cached when search is being repeated)
Please note that this article was reproduced with permission from Bill Beckelman's website. The original article can be found here. This guide has been used succesfully with Drupal.
2. Download Solr 1.4.1 from one of the mirrors at http://www.apache.org/dyn/closer.cgi/lucene/solr/
(at the time of writing, not all mirrors seem to be hosting 1.4.1, but most seem
to have at least 1.4.0)
In order to use these directions, you must have access to the your Apache Solr installation including solrconfig.xml and elevate.xml.
By default, Apache Solr does not use the QueryElevationComponent (which enables the administrator to manipulate query results) in the default request handler. This page is a guide on how to use QueryElevationComponent to artificially promote nodes based on a search query.