I just noticed your 1st of a series of articles on WebService::Solr. Looks great so far! :)

Here are some comments about the code:

In the first script, you could probably use the much simpler syntax for add() rather than then full-on OOP way with Document and Field objects:

my $id  = WebService::Solr::Field->new( id  => $index );
my $title = WebService::Solr::Field->new( title => $_ );
my $doc = WebService::Solr::Document->new;
$doc->add_fields(( $id, $title ));
$solr->add( $doc );
$solr->commit;

could be as simple as:

$solr->add( { id => $index, title => $_ } );

The full object notation is available when you need it, but for simple docs, I wouldn’t bother with it.

Also, note that I’ve left off the call to commit(). WebService::Solr has an “autocommit” bit that is on by default, so, after operations that require a commit, it’s already done for you.

I should probably also mention that it would be more efficient to send multiple documents over the line rather than one at a time — though this case wouldn’t show much difference.

In the searching script you write:

print "Your search ($query) found " . ( $#hits + 1 ) . " document(s).\n\n";

While this is true for this particular index, in reality

my @hits = $response->docs;

only returns the documents attached to this particular response — which could be, for example, 10 out of 100 actual results.

The true number of matches can be found with the pager object:

$response->pager->total_entries

Hopefully I’m not giving you a bunch of details that you’re already aware of — If i am, I apologize.

Anyway, I can’t wait for the rest of the series! :)

“Thanks, Brian!