Lucene, Nutch and Solr

Thanks in large part to the talented Nick_vh who is interning with Acquia as the final stage of his master's degree, we've been making progress on a number of outstanding issues for apachesolr 7.x. If you are using the module, please take a look at http://drupal.org/node/1293570 which lists remaining issues to be included in the next beta release (possibly the end of this week).

The patch to improve custom search pages includes a number of re-arrangements for the UI, so please try it out: http://drupal.org/node/1294846

After the first super-nerdy Drupal Tech Talk in Rotterdam, Hoppinger, Proteon and Triquanta kindly invite you to the second Drupal Tech Talk on September 22nd at the Proteon offices in Delft, the Netherlands. The Drupal Tech Talk is a meetup specifically targeted at Drupal developers in Belgium and the Netherlands. The talks and sessions dive deep technically. You can count on poorly designed slides with lots of code and risky live demos.

I am using Apachesolr module with Drupal 6. I have only one facet so far on my searching and that is the node type. I have a list of links that is supposed to filter the query. When I put in a search term, I get all the matching results and the list of links with the correct counts for each node type. However, when I click a node type it returns just the result for that node type, but now all the counts in my link list have turned to 0, except for that node type which shows the correct amount, I have it set a $_REQUEST['filter'] parameter.

I have a site that is based on Open Atrium and currently using solr for site search. I would like to be able to add organic group members to the search index so that I can search for users within a particular OG. I would appreciate suggestions on how best to approach this.

Solr is set up via the Chapter 3 open atrium features module here http://features.chapterthree.com/openatrium-apachesolr-search/1-0-0, which uses apachesolr, apachesolr_og, apachesolr_search, and apachesolr_nodeaccess. In addition, Open Atrium uses nodeprofile so users' profiles are already in the index.

What I have considered doing is adding users' profile nodes to the same groups that they belong to. This would then make them searchable by OG, however my concern is that I would like everyone to be able to search for users across all OGs, including private OGs, and this would result in permission issues.

I would really appreciate any suggestions. Thanks.

The Problem

The search community is fragmented. The problem stems from a core search module that doesn't facilitate third party backends, so each project is forced to solve similar problems in slightly different ways. Each contributed module has its own isolated sub-community, which is detrimental to Drupal as a whole.

transferred from http://drupal.org/node/1090080

Please Make your notes or changes inline, preferably to reflect IRC or other more rea-time discussions.

We had a BoF and many discussion at Drupalcon Chicago 2011, here's the take away:

<

ul>

We have a website which is mostly English, but some of the fields in some of our content types are in another language. This other language has different rules for alphabetization, etc. We'd like to be able to sort searches on these fields using the appropriate locale.

You can do this in the Solr schema.xml file by adding the appropriate locale="..." attribute to the field definitions. I'm wondering whether there's a way to do this through the Drupal API, so that we don't need to modify the schema.xml file. Has anyone else looked into this idea?

Hey,

i already created an issue but got no reaction. Someone here using apachesolr_views? If yes please tell me which version of views you use (or which dev snapshot). I tried 6.x-3.x-dev and alpha3 but report errors.

regards Volkan

Hello,

I'm about to move from development to launch on a project that uses solr to index around 800,000 nodes. At present it is on a dedicated server with 4gb ram, along with about 15 other websites I host. It is clear that under load I am experiencing slow downs in mySQL from a lack of memory, and from what I've read it appears the RAM allocated to Solr is a major factor in how fast and responsive your solr searches are.

What I'd like to know is

• Should I be aiming to upgrade this server with more memory, or to launch a new box that is dedicated to mysql/solr/both?