amrsoliman / elasticquent
Maps Laravel Eloquent models to Elasticsearch types.
Requires
- php: >=5.4.0
- elasticsearch/elasticsearch: 5.1.*
- illuminate/config: ~4.2|^5
- illuminate/database: ~4.2|^5
- jsq/amazon-es-php: 0.2.0
- nesbot/carbon: ~1.0
Requires (Dev)
- mockery/mockery: ^0.9.4
- phpunit/phpunit: ~5.0
README
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
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.
$books = Book::where('id', '<', 200)->get(); $books->addToIndex();
When you search, instead of getting a plain array of search results, you instead get an Eloquent collection with some special Elasticsearch functionality.
$books = Book::search('Moby Dick')->get(); echo $books->totalHits();
Plus, you can still use all the Eloquent collection functionality:
$books = $books->filter(function($book) { return $book->hasISBN(); });
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
, add the Elasticquent trait to any Eloquent model that you want to be able to index in Elasticsearch:
use Elasticquent\ElasticquentTrait; class Book extends Eloquent { use ElasticquentTrait; }
Now your Eloquent model has some extra methods that make it easier to index your model's data using Elasticsearch.
Elasticsearch Configuration
If you need to pass a special configuration array Elasticsearch, you can add that in an elasticquent.php
config file at /app/config/elasticquent.php
for Laravel 4, or /config/elasticquent.php
for Laravel 5:
<?php return array( /* |-------------------------------------------------------------------------- | Custom Elasticsearch Client Configuration |-------------------------------------------------------------------------- | | This array will be passed to the Elasticsearch client. | See configuration options here: | | http://www.elasticsearch.org/guide/en/elasticsearch/client/php-api/current/_configuration.html */ 'config' => [ 'hosts' => ['localhost:9200'], 'retries' => 1, ], /* |-------------------------------------------------------------------------- | Default Index Name |-------------------------------------------------------------------------- | | This is the index name that Elastiquent will use for all | Elastiquent models. */ 'default_index' => 'my_custom_index_name', );
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 mapping, you can set a mappingProperties
property in your model and use some mapping functions from there:
protected $mappingProperties = array( 'title' => array( 'type' => 'string', 'analyzer' => 'standard' ) );
If you'd like to setup a model's type mapping based on your mapping properties, you can use:
Book::putMapping($ignoreConflicts = true);
To delete a mapping:
Book::deleteMapping();
To rebuild (delete and re-add, useful when you make important changes to your mapping) a mapping:
Book::rebuildMapping();
You can also get the type mapping and check if it exists.
Book::mappingExists(); Book::getMapping();
Setting a Custom Index Name
Elastiquent will use default
as your index name, but you can set a custom index name by creating an elasticquent.php
config file in /app/config/
:
<?php return array( /* |-------------------------------------------------------------------------- | Default Index Name |-------------------------------------------------------------------------- | | This is the index name that Elastiquent will use for all | Elastiquent models. */ 'default_index' => 'my_custom_index_name', );
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.
function getTypeName() { return 'custom_type_name'; }
To check if the type for the Elasticquent model exists yet, use typeExists
:
$typeExists = Book::typeExists();
Indexing Documents
To index all the entries in an Eloquent model, use addAllToIndex
:
Book::addAllToIndex();
You can also index a collection of models:
$books = Book::where('id', '<', 200)->get(); $books->addToIndex();
You can index individual entries as well:
$book = Book::find($id); $book->addToIndex();
You can also reindex an entire model:
Book::reindex();
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.
$books = Book::search('Moby Dick');
Query Based Search
The second is a query based search for more complex searching needs:
public static function searchByQuery($query = null, $aggregations = null, $sourceFields = null, $limit = null, $offset = null, $sort = null)
Example:
$books = Book::searchByQuery(array('match' => array('title' => 'Moby Dick')));
Here's the list of available parameters:
query
- Your ElasticSearch Queryaggregations
- The Aggregations you wish to return. See Aggregations for details.sourceFields
- Limits returned set to the selected fields onlylimit
- Number of records to returnoffset
- 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:
$books = Book::complexSearch(array( 'body' => array( 'query' => array( 'match' => array( 'title' => 'Moby Dick' ) ) ) ));
This is the equivalent to:
$books = Book::searchByQuery(array('match' => array('title' => 'Moby Dick')));
Search Collections
When you search on an Elasticquent model, you get a search collection with some special functions.
You can get total hits:
$books->totalHits();
Access the shards array:
$books->shards();
Access the max score:
$books->maxScore();
Access the timed out boolean property:
$books->timedOut();
And access the took property:
$books->took();
And access search aggregations - See Aggregations for details:
$books->getAggregations();
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:
$book->isDocument();
You can check the document score that Elasticsearch assigned to this document with:
$book->documentScore();
Chunking results from Elastiquent
Similar to Illuminate\Support\Collection
, the chunk
method breaks the Elasticquent collection into multiple, smaller collections of a given size:
$all_books = Book::searchByQuery(array('match' => array('title' => 'Moby Dick'))); $books = $all_books->chunk(10);
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.
$client = new \Elasticsearch\Client(); $params = array( 'index' => 'default', 'type' => 'books' ); $params['body']['query']['match']['title'] = 'Moby Dick'; $collection = new \Elasticquent\ElasticquentResultCollection($client->search($params), new Book);
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.
function getIndexDocumentData() { return array( 'id' => $this->id, 'title' => $this->title, 'custom' => 'variable' ); }
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
.
class MyCollection extends \Illuminate\Database\Eloquent\Collection { use ElasticquentCollectionTrait; }
Deleting Documents in A type:
If you are using elastic version >= 2, you have to install delete-by-query plugin
delete All Document
Book::deleteAllDocuments();
delete Document By Query
$query = array('match' => array('is_published' => 0)); Book::deleteDocuments($query);
Roadmap
Elasticquent currently needs:
- Tests that mock ES API calls.
- Support for routes