Elasticsearch Support
Overview
Elasticsearch is a distributed RESTful search and analytics engine capable of solving a growing number of use cases: application search, security analytics, metrics, logging, etc.
API Platform comes natively with the reading support for Elasticsearch. It uses internally the official PHP client for Elasticsearch: Elasticsearch-PHP.
Be careful, API Platform only supports Elasticsearch >= 7.11.0 < 8.0.
Enabling Reading Support
To enable the reading support for Elasticsearch, simply require the Elasticsearch-PHP package using Composer:
composer require elasticsearch/elasticsearch:^7.11Then, enable it inside the API Platform configuration:
# api/config/packages/api_platform.yaml
parameters:
# ...
env(ELASTICSEARCH_HOST): 'http://localhost:9200'
api_platform:
# ...
mapping:
paths: ['%kernel.project_dir%/src/Model']
elasticsearch:
hosts: ['%env(ELASTICSEARCH_HOST)%']
#...Creating Models
API Platform follows the best practices of Elasticsearch:
- a single index per resource should be used because Elasticsearch is going to drop support for index types and will allow only a single type per index;
- index name should be the short resource name in lower snake case;
- the default
_doctype should be used; - all fields should be lower case and should use camel case for combining words.
This involves having mappings and models which absolutely match each other.
Here is an example of mappings for 2 resources, User and Tweet, and their models:
PUT user
{
"mappings": {
"_doc": {
"properties": {
"id": {
"type": "keyword"
},
"gender": {
"type": "keyword"
},
"age": {
"type": "integer"
},
"first_name": {
"type": "text"
},
"last_name": {
"type": "text"
},
"tweets": {
"type": "nested",
"properties": {
"id": {
"type": "keyword"
},
"date": {
"type": "date",
"format": "yyyy-MM-dd HH:mm:ss"
},
"message": {
"type": "text"
}
},
"dynamic": "strict"
}
},
"dynamic": "strict"
}
}
}PUT tweet
{
"mappings": {
"_doc": {
"properties": {
"id": {
"type": "keyword"
},
"author": {
"properties": {
"id": {
"type": "keyword"
},
"gender": {
"type": "keyword"
},
"age": {
"type": "integer"
},
"first_name": {
"type": "text"
},
"last_name": {
"type": "text"
}
},
"dynamic": "strict"
},
"date": {
"type": "date",
"format": "yyyy-MM-dd HH:mm:ss"
},
"message": {
"type": "text"
}
},
"dynamic": "strict"
}
}
}<?php
// api/src/Model/User.php
namespace App\Model;
use ApiPlatform\Elasticsearch\State\CollectionProvider;
use ApiPlatform\Elasticsearch\State\ItemProvider;
use ApiPlatform\Elasticsearch\State\Options;
use ApiPlatform\Metadata\ApiProperty;
use ApiPlatform\Metadata\ApiResource;
use ApiPlatform\Metadata\Get;
use ApiPlatform\Metadata\GetCollection;
#[ApiResource(
operations: [
new GetCollection(provider: CollectionProvider::class, stateOptions: new Options(index: 'user')),
new Get(provider: ItemProvider::class, stateOptions: new Options(index: 'user')),
],
)]
class User
{
#[ApiProperty(identifier: true)]
public string $id = '';
public string $gender;
public int $age;
public string $firstName;
public string $lastName;
/**
* @var Tweet[]
*/
public iterable $tweets = [];
}<?php
// api/src/Model/Tweet.php
namespace App\Model;
use ApiPlatform\Elasticsearch\State\CollectionProvider;
use ApiPlatform\Elasticsearch\State\ItemProvider;
use ApiPlatform\Elasticsearch\State\Options;
use ApiPlatform\Metadata\ApiProperty;
use ApiPlatform\Metadata\ApiResource;
use ApiPlatform\Metadata\Get;
use ApiPlatform\Metadata\GetCollection;
#[ApiResource(
operations: [
new GetCollection(provider: CollectionProvider::class, stateOptions: new Options(index: 'tweet')),
new Get(provider: ItemProvider::class, stateOptions: new Options(index: 'tweet')),
],
)]
class Tweet
{
#[ApiProperty(identifier: true)]
public string $id = '';
public User $author;
public \DateTimeInterface $date;
public string $message;
}API Platform will automatically disable write operations and snake case document fields will automatically be converted to camel case object properties during serialization.
Keep in mind that it is your responsibility to populate your Elasticsearch index. To do so, you can use Logstash, a custom state processors or any other mechanism that suits your project (such as an ETL).
You're done! The API is now ready to use.
Filtering
See how to use Elasticsearch filters and how to create Elasticsearch custom filters in the Filters chapter.
Creating Custom Extensions
See how to create Elasticsearch custom extensions in the Extensions chapter.
