Lucene, Nutch and Solr

Hi,

Can anyone let me know if it is possible to index and search multiple Drupal and non-drupal websites using the ApacheSolr module?

If not please let me know of any other way that this could be achieved.

Thanks

Overview

This project is about adding RDF Support to the popular ApacheSolr module in the form of a Solr RDF contrib module. The module should be able to read an RDF class specification and automatically generate the necessary mapping to a Solr server, provide the capability to search resources with that type and also generate facets based on its properties. It would even be possible to build the existing Node search capabilites completely on top of this mechanism! But in any case you could also add arbitrary other types like users or taxonomy terms, or resources from other websites altogether.

Just wanted to write to get the views of all here on the opensearchclient module.

I've recently been handed the task of porting a hacked version (was done previously, not by me) of the opensearchclient module which is needed for a site I'm upgrading to D6. The hacked version has been ported, and I noticed the original code has been abandoned.

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!

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/

We have a database Server Configuration:
4GB RAM
600GB Hard Disk
Xeon Processor 1.3 Ghz.

We are barely able to have 100 concurrent users!!! What are we doing wrong.

I know I need to configure mysql_query cache, mysql_limit_size and table_cache. But what should be the formula, and how do we go about checking the same.

Below is the details of our my.ini file.

[mysqld]
datadir=/database/data
socket=/var/lib/mysql/mysql.sock
set-variable=max_connections=2000
set-variable = max_allowed_packet=64M
default-storage-engine = innodb
log-bin=/database/data/mysql-bin

Could you validate our Scenarios and the Server configurations. We will share the results with the community soon.

BENCH MARK SCENARIOS:

The Scenarios:

Drupal 6.0 Search + Statistics + simul. Cron + replication
SolR Search + Statistics + simul. Cron + replication
Drupal 6.0 Search/ Solr Search with Statistics + replication
Drupal 6.0 Search/ Solr Search + simul. Cron + replication

Server Configuration:

Drupal Site and DB are to be placed in two Dual core servers with 4 GB RAM each

Software details: Linux - RHEL 5 , Apache 2.2.3, MySQL Enterperise 5, PHP 5.1.6

Need some clarifications on the best search algorithms to use. I work with a Netlink Technologies. We are currently planning to have a Architect a large Job portal in Drupal. Have convinced our organization that we use Drupal 6.0 and create custom nodes and modules. We are also planning on bench marking the different options of Search that we could adopt.

For Search we are just trying to understand ApacheSolr and Sphinx search.

DO you think we are proceeding in the right direction. Will Drupal - SOLR be a scalable option for a large job portal?

Shyamala
Tech Head