Solr

Hi,

Has anyone managed to display the output of a solr search on a map? Using either gmap, openlayers, etc.

Also has anyone got spatial search / local search working with UK postcodes?

Been trying for a week now with no success - can get core drupal search + facets working with proximity and map output but solr is so much better!

TIA

We need to implement html node titles with bbcode (as per http://drupal.org/node/28537) for a client site that's using ApacheSolr. The titles need to be displayed in search results with their html intact so the bbcode version has to get indexed. I need to tell Solr to ignore this code when trying to match queries. For example, if a user searches for "blue smurf" (with the quotation marks), and there's a node with the title "[strong]blue[/strong] smurf" in the index, Solr needs to recognise this as a match.

I have had a lot of research about optimizing Apachesolr for non-english languages, especially for German. It comes out, that there search results can be dramatically improved by adjusting Solr's stemming and by breaking up compound words. This can be easily achieved with slight changes to Apachesolr's schema.xml.

This post is about configuring stemming:
http://www.early-dance.de/news/9188-optimizing-apachesolr-non-english-la...

And this post is about compound word splitting, that is needed in languages like German that have long combined words like "Dampfschifffahrt":
http://www.early-dance.de/news/9189-apachesolr-issues-german-and-other-g...

Hi Everyone,

Today I took a couple hours and attempted a backport of ApacheSolr D6 to D5. This will bring all of the cool features that D6 has to D5. The patch needs work. It doesn't yet work. If anyone has time to chip in and work on the indexing of nodes (currently not working) that'd be great. With a little momentum I think we can do the backport relatively quickly, after which keeping the two in sync will be much easier.

http://drupal.org/node/337735#comment-1240921

Just want to share my experience with using the apachesolr module as an API. I use apachesolr module purely as interface between my own drupal modules and the Solr instance. Part of the reason to do so is that I use a different schema.xml, compared to the one provided with the apachesolr module.

For the single technical detail, read this issue.

Thanks a lot to the developers for creating the apachesolr module and making it nicely extensible!

I was looking for a way to run Solr as a service on Debian. Ez Publish CMS has some interesting scripts in their svn repository http://svn.ez.no/svn/extensions/ezfind/ezp4/trunk/extension/ezfind/bin/s...
http://svn.ez.no/svn/extensions/ezfind/ezp4/trunk/extension/ezfind/java/

I used the solr script from the first link together with the solr.sh in the second, followed the instructions in the solr script and it works well.

Somebody another or better solution?

Query 1:

field1:value1 field2:value2

Query 1 reversed:

field2:value2 field1:value1

.

Does it make a difference? Would it be better for performance to use the field first which yields the smallest sub result set? Or does Solr/Lucene handle this all by itself?

Check out this awesome jQuery/Solr library that David Peterson pointed me to: http://solrjs.solrstuff.org/test/reuters/

Last night we enabled Pivots recommendations on Drupal.org. We've been working on Pivots for almost 18 months and I think it represents an exciting new type of Drupal.org service. Today pivots uses a custom indexer written in Java. That indexer reads the content on Drupal.org and then indexes it to the masterdb-other.drupal.org a database server outside our main Drupal.org database servers.

See: http://mrzhou.cms.si.umich.edu/diagram-pivots-recommendation-system-do

Now that [edit Solr ] apachesolr has moved on considerably, I was wondering if anyone has used it's full text indexing of documents combined with the taxonomy, and access control of drupal as part of a DMS.

I tried this a year ago, couldnt get it working and ended up with a Knowledge Tree/Drupal integrated solution, which seems good at the time, but in use was too disparate. I want it in Drupal (!), not another system.