Using Solarium with SOLR for Search - Solarium and GUI

This article, the second in a four-part series, details using Solarium with Apache SOLR for search functionality. The first part covered core concepts, installation, and setup. This part focuses on Solarium installation, building a sample application, populating the search index, and preparing for search queries.

Key Concepts:

• Solarium provides an abstraction layer over SOLR, simplifying development by making SOLR appear as a local search implementation.
• Connecting Solarium requires providing host, port, and path details for the SOLR server.
• Solarium simplifies adding, updating, and deleting documents using update query instances. Updates are handled by "re-adding" documents with the same unique identifier.
• This guide walks through application creation, Solarium configuration, ping queries, sample data addition, and search index population. It also shows creating a search form using Laravel's Blade templating.

Application Creation & Solarium Installation:

Create a new Laravel application:

composer create-project laravel/laravel movie-search --prefer-dist

Make the app/storage directory writable. Install Solarium via Composer:

"solarium/solarium": "dev-develop"

(Alternatively, download or clone from GitHub.) Add this to your composer.json file.

Solarium Configuration:

Create a configuration file (app/config/solr.php):

return array(
    'host'      => '127.0.0.1',
    'port'      => 8983,
    'path'      => '/solr/',
);

For simplicity, create a Solarium client instance as a controller property (app/controllers/HomeController.php):

    protected $client;

    public function __construct()
    {
        $this->client = new \Solarium\Client(Config::get('solr'));
    }

(In a larger Laravel app, a service provider would be preferred.)

Ping Queries & Sample Data:

Use ping queries to verify SOLR accessibility:

$ping = $client->createPing();
try {
    $result = $client->ping($ping);
} catch (Solarium\Exception $e) {
    // Handle SOLR inaccessibility
}

A sample movie CSV file (containing ~2000 movies) is needed. You can download one, or use the Rotten Tomatoes API (IMDB data is also available but less conveniently).

Adding, Updating, and Deleting Documents:

Adding a document:

$update = $client->createUpdate();
$doc = $update->createDocument();
$doc->id = 123;
$doc->title = 'Some Movie';
$update->addDocument($doc);
$update->addCommit();
$result = $client->update($update);

Updating requires re-adding with the same ID. Deleting uses addDeleteQuery:

$update = $client->createUpdate();
$update->addDeleteQuery('id:123'); // Or use wildcards: 'title:test*'
$update->addCommit();
$result = $client->update($update);

Populating the Search Index:

Create a Laravel command (php artisan command:make PopulateSearchIndexCommand) to import the CSV data. In app/commands/PopulateSearchIndexCommand.php, use the fire() method to read the CSV, create Solarium documents, and index them. (The provided code example shows this process.) Run the command: php artisan search:populate.

The Search Form (Laravel Blade):

Create a search form in app/views/home/index.blade.php:

composer create-project laravel/laravel movie-search --prefer-dist

(A basic layout in app/views/layouts/default.blade.php and routing in app/routes.php are also needed, as shown in the original example.)

Conclusion:

This article sets the stage for building a search mechanism using Solarium and SOLR. The next part will cover implementing the actual search functionality. The provided FAQs section has been omitted as it's redundant given the detailed explanation already provided.

The above is the detailed content of Using Solarium with SOLR for Search - Solarium and GUI. For more information, please follow other related articles on the PHP Chinese website!