Skip to content
  • Documentation >
  • Search >
  • Extend search >
  • Customize Elasticsearch index structure

Customize Elasticsearch index structure

You can customize the structure of your Elasticsearch search index to manage how documents in the index are grouped.

This lets you control the size of Elasticsearch shards that the index is divided into.

By customizing the structure to your needs, you can avoid "oversharding" (having too many shards), which negatively affects performance and can lead to instability.

Sizing Elasticsearch shards

See Elasticsearch documentation for more information about adapting the size of your search index shards.

Selecting indexing strategy

In your Elasticsearch configuration you can select one of four built-in strategies that control grouping documents in the index.

The strategies are:

  • NullGroupResolver - groups all documents into a single group.
  • LanguageGroupResolver - groups documents by language code.
  • ContentTypeGroupResolver- groups documents by content type ID.
  • CompositeGroupResolver - allows combining multiple group resolves together to have a more granular index.

The default strategy is the composite of language and content type ID, resulting in indexes in the form of <repository>_<document_type>_<language>_<content_type_id>.

To change the strategy, use the ibexa_elasticsearch.document_group_resolver configuration key:

1
2
ibexa_elasticsearch:
    document_group_resolver: 'Ibexa\Elasticsearch\ElasticSearch\Index\Group\ContentTypeGroupResolver'

Select the strategy based on the structure of your Repository, taking into accounts data such as the number of content items, content types or languages.

Custom indexing strategy

You can also create a group resolver that provides a custom indexing strategy. This resolver must implement Ibexa\Contracts\Elasticsearch\ElasticSearch\Index\Group\GroupResolverInterface.

Create group resolver

In this example, create a ContentTypeGroupGroupResolver based on the content type Group ID of the document:

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
<?php

declare(strict_types=1);

namespace App\GroupResolver;

use Ibexa\Contracts\Core\Persistence\Content\Type\Handler;
use Ibexa\Contracts\Elasticsearch\ElasticSearch\Index\Group\GroupResolverInterface;
use Ibexa\Contracts\Elasticsearch\Mapping\BaseDocument;

final class ContentTypeGroupGroupResolver implements GroupResolverInterface
{
    private Handler $contentTypeHandler;

    public function __construct(Handler $contentTypeHandler)
    {
        $this->contentTypeHandler = $contentTypeHandler;
    }

    public function resolveDocumentGroup(BaseDocument $document): string
    {
        $index = $this->contentTypeHandler->load($document->contentTypeId)->groupIds[0];

        return (string)$index;
    }
}

Register the resolver as a service:

1
2
3
4
services:
    App\GroupResolver\ContentTypeGroupGroupResolver:
        arguments:
            $contentTypeHandler: '@Ibexa\Contracts\Core\Persistence\Content\Type\Handler'

Configure indexing strategy

Finally, in configuration indicate that Elasticsearch should use your custom indexing strategy:

1
2
ibexa_elasticsearch:
    document_group_resolver: 'App\GroupResolver\ContentTypeGroupGroupResolver'