Download the PHP package reallyli/elasticquent without Composer

Elasticquent

Elasticsearch for Eloquent Laravel Models

Elasticquent makes working with Elasticsearch and Eloquent models easier by mapping them to Elasticsearch types. You can use the default settings or define how Elasticsearch should index and search your Eloquent models right in the model.

Elasticquent uses the official Elasticsearch PHP API. To get started, you should have a basic knowledge of how Elasticsearch works (indexes, types, mappings, etc).

Elasticsearch Requirements

You must be running at least Elasticsearch 1.0. Elasticsearch 0.9 and below will not work and are not supported.

Contents

• Overview
  • How Elasticquent Works
• Setup
  • Elasticsearch Configuration
  • Indexes and Mapping
  • Setting a Custom Index Name
  • Setting a Custom Type Name
• Indexing Documents
• Searching
  • Search Collections
  • Search Collection Documents
  • Chunking results from Elastiquent
  • Using the Search Collection Outside of Elasticquent
• More Options
  • Document Ids
  • Document Data
  • Using Elasticquent With Custom Collections
• Roadmap

Reporting Issues

If you do find an issue, please feel free to report it with GitHub's bug tracker for this project.

Alternatively, fork the project and make a pull request :)

Overview

Elasticquent allows you take an Eloquent model and easily index and search its contents in Elasticsearch.

When you search, instead of getting a plain array of search results, you instead get an Eloquent collection with some special Elasticsearch functionality.

Plus, you can still use all the Eloquent collection functionality:

Check out the rest of the documentation for how to get started using Elasticsearch and Elasticquent!

How Elasticquent Works

When using a database, Eloquent models are populated from data read from a database table. With Elasticquent, models are populated by data indexed in Elasticsearch. The whole idea behind using Elasticsearch for search is that its fast and light, so you model functionality will be dictated by what data has been indexed for your document.

Setup

Before you start using Elasticquent, make sure you've installed Elasticsearch.

To get started, add Elasticquent to you composer.json file:

"elasticquent/elasticquent": "dev-master"

Once you've run a composer update, you need to register Laravel service provider, in your config/app.php:

We also provide a facade for elasticsearch-php client (which has connected using our settings), add following to your config/app.php if you need so.

Then add the Elasticquent trait to any Eloquent model that you want to be able to index in Elasticsearch:

Now your Eloquent model has some extra methods that make it easier to index your model's data using Elasticsearch.

Elasticsearch Configuration

By default, Elasticquent will connect to localhost:9200 and use default as index name, you can change this and the other settings in the configuration file. You can add the elasticquent.php config file at /app/config/elasticquent.php for Laravel 4, or use the following Artisan command to publish the configuration file into your config directory for Laravel 5:

Indexes and Mapping

While you can definitely build your indexes and mapping through the Elasticsearch API, you can also use some helper methods to build indexes and types right from your models.

If you want a simple way to create indexes, Elasticquent models have a function for that:

Book::createIndex($shards = null, $replicas = null);

For custom analyzer, you can set an indexSettings property in your model and define the analyzers from there:

For mapping, you can set a mappingProperties property in your model and use some mapping functions from there:

If you'd like to setup a model's type mapping based on your mapping properties, you can use:

To delete a mapping:

To rebuild (delete and re-add, useful when you make important changes to your mapping) a mapping:

You can also get the type mapping and check if it exists.

Setting a Custom Index Name

By default, Elasticquent will look for the default_index key within your configuration file(config/elasticquent.php). To set the default value for an index being used, you can edit this file and set the default_index key:

If you'd like to have a more dynamic index, you can also override the default configuration with a getIndexName method inside your Eloquent model:

Note: If no index was specified, Elasticquent will use a hardcoded string with the value of default.

Setting a Custom Type Name

By default, Elasticquent will use the table name of your models as the type name for indexing. If you'd like to override it, you can with the getTypeName function.

To check if the type for the Elasticquent model exists yet, use typeExists:

Indexing Documents

To index all the entries in an Eloquent model, use addAllToIndex:

You can also index a collection of models:

You can index individual entries as well:

You can also reindex an entire model:

Searching

There are three ways to search in Elasticquent. All three methods return a search collection.

Simple term search

The first method is a simple term search that searches all fields.

Query Based Search

The second is a query based search for more complex searching needs:

Example:

Here's the list of available parameters:

• query - Your ElasticSearch Query
• aggregations - The Aggregations you wish to return. See Aggregations for details.
• sourceFields - Limits returned set to the selected fields only
• limit - Number of records to return
• offset - Sets the record offset (use for paging results)
• sort - Your sort query

Raw queries

The final method is a raw query that will be sent to Elasticsearch. This method will provide you with the most flexibility when searching for records inside Elasticsearch:

This is the equivalent to:

Search Collections

When you search on an Elasticquent model, you get a search collection with some special functions.

You can get total hits:

Access the shards array:

Access the max score:

Access the timed out boolean property:

And access the took property:

And access search aggregations - See Aggregations for details:

Search Collection Documents

Items in a search result collection will have some extra data that comes from Elasticsearch. You can always check and see if a model is a document or not by using the isDocument function:

You can check the document score that Elasticsearch assigned to this document with:

Chunking results from Elastiquent

Similar to Illuminate\Support\Collection, the chunk method breaks the Elasticquent collection into multiple, smaller collections of a given size:

Using the Search Collection Outside of Elasticquent

If you're dealing with raw search data from outside of Elasticquent, you can use the Elasticquent search results collection to turn that data into a collection.

More Options

Document IDs

Elasticquent will use whatever is set as the primaryKey for your Eloquent models as the id for your Elasticsearch documents.

Document Data

By default, Elasticquent will use the entire attribute array for your Elasticsearch documents. However, if you want to customize how your search documents are structured, you can set a getIndexDocumentData function that returns you own custom document array.

Be careful with this, as Elasticquent reads the document source into the Eloquent model attributes when creating a search result collection, so make sure you are indexing enough data for your the model functionality you want to use.

Using Elasticquent With Custom Collections

If you are using a custom collection with your Eloquent models, you just need to add the ElasticquentCollectionTrait to your collection so you can use addToIndex.

Roadmap

Elasticquent currently needs:

• Tests that mock ES API calls.
• Support for routes