The package provides the perfect starting point to integrate ElasticSearch into your Laravel application. It is carefully crafted to simplify the usage of ElasticSearch within the Laravel Framework.
It’s built on top of the latest release of Laravel Scout, the official Laravel search package. Using this package, you are free to take advantage of all of Laravel Scout’s great features, and at the same time leverage the complete set of ElasticSearch’s search experience.
If you need any help, stack overflow is the preferred and recommended way to ask support questions.
Don't forget to ⭐ the package if you like it. 🙏
- Search amongst multiple models
- Zero downtime reimport - it’s a breeze to import data in production.
- Eager load relations - speed up your import.
- Elasticsearch 7.4 support
- Import all searchable models at once.
- A fully configurable mapping for each model.
- Full power of ElasticSearch in your queries.
- PHP version >= 7.1.3
- Laravel Framework version >= 5.6
| Elasticsearch version | ElasticsearchDSL version |
|---|---|
| >= 7.0 | >= 3.0.0 |
| >= 6.0, < 7.0 | < 3.0.0 |
Use composer to install the package:
composer require matchish/laravel-scout-elasticsearch
Set env variables
SCOUT_DRIVER=Matchish\ScoutElasticSearch\Engines\ElasticSearchEngine
The package uses \ElasticSearch\Client from official package, but does not try to configure it,
so feel free do it in your app service provider.
But if you don't want to do it right now,
you can use Matchish\ElasticSearchServiceProvider from the package.
Register the provider, adding to config/app.php
'providers' => [
// Other Service Providers
\Matchish\ScoutElasticSearch\ElasticSearchServiceProvider::class
],
Set ELASTICSEARCH_HOST env variable
ELASTICSEARCH_HOST=host:port
And publish config example for elasticsearch
php artisan vendor:publish --tag config
Note: This package adds functionalities to Laravel Scout, and for this reason, we encourage you to read the Scout documentation first. Documentation for Scout can be found on the Laravel website.
It is very important to define the mapping when we create an index — an inappropriate preliminary definition and mapping may result in the wrong search results.
To define mappings or settings for index, set config with right value.
For example if method searchableAs returns
products string
Config key for mappings should be
elasticsearch.indices.mappings.products
Or you you can specify default mappings with config key
elasticsearch.indices.mappings.default
Same way you can define settings
For index products it will be
elasticsearch.indices.settings.products
And for default settings
elasticsearch.indices.settings.default
To speed up import you can eager load relations on import using global scopes.
You should configure ImportSourceFactory in your service provider(register method)
use Matchish\ScoutElasticSearch\Searchable\ImportSourceFactory;
...
public function register(): void
{
$this->app->bind(ImportSourceFactory::class, MyImportSourceFactory::class);
Here is an example of MyImportSourceFactory
namespace Matchish\ScoutElasticSearch\Searchable;
final class MyImportSourceFactory implements ImportSourceFactory
{
public static function from(string $className): ImportSource
{
//Add all required scopes
return new DefaultImportSource($className, [new WithCommentsScope()]);
}
}
class WithCommentsScope implements Scope {
/**
* Apply the scope to a given Eloquent query builder.
*
* @param \Illuminate\Database\Eloquent\Builder $builder
* @param \Illuminate\Database\Eloquent\Model $model
* @return void
*/
public function apply(Builder $builder, Model $model)
{
$builder->with('comments');
}
}
While working in production, to keep your existing search experience available while reimporting your data, you also can use scout:import Artisan command:
php artisan scout:import
The command create new temporary index, import all models to it, and then switch to the index and remove old index.
To be fully compatible with original scout package, this package does not add new methods.
So how we can build complex queries?
There is two ways.
By default, when you pass a query to the search method, the engine builds a query_string query, so you can build queries like this
Product::search('title:this OR description:this) AND (title:that OR description:that')`If it's not enough in your case you can pass a callback to the query builder
$results = Product::search('zonga', function($client, $body) {
$minPriceAggregation = new MinAggregation('min_price');
$minPriceAggregation->setField('price');
$maxPriceAggregation = new MaxAggregation('max_price');
$maxPriceAggregation->setField('price');
$brandTermAggregation = new TermsAggregation('brand');
$brandTermAggregation->setField('brand');
$body->addAggregation($minPriceAggregation);
$body->addAggregation($brandTermAggregation);
return $client->search(['index' => 'products', 'body' => $body->toArray()]);
})->raw();$client is \ElasticSearch\Client object from elasticsearch/elasticsearch package
And $body is ONGR\ElasticsearchDSL\Search from ongr/elasticsearch-dsl package
You can do it with Mixed class, just pass indices names separated by commas to the within method.
Mixed::search('title:Barcelona or to:Barcelona')
within(implode(',', [
(new Ticket())->searchableAs(),
(new Book())->searchableAs(),
]))
->get();In this example you will get collection of Ticket and Book models where ticket's arrival city or
book title is Barcelona
Often your response isn't collection of models but aggregations or models with higlights an so on.
In this case you need to implement your own implementation of HitsIteratorAggregate and bind it in your service provider
Scout ElasticSearch is an open-sourced software licensed under the MIT license.