Devil Killer Is Here MiNi Shell
MiNi SheLL

Current Path : /home/vmanager/www/vendor_kopia_11_08_2023/yiisoft/yii2-elasticsearch/docs/guide/
Linux eb5096292c53 5.15.0-102-generic #112-Ubuntu SMP Tue Mar 5 16:50:32 UTC 2024 x86_64
Current File : /home/vmanager/www/vendor_kopia_11_08_2023/yiisoft/yii2-elasticsearch/docs/guide/mapping-indexing.md
# Mapping & Indexing

## Comparison with SQL

[Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/_mapping_concepts_across_sql_and_elasticsearch.html) provides an extensive list of concepts in Elasticsearch and SQL and how they map to one another. We'll focus on the
basics.

An Elasticsearch cluster consists of one or more Elasticsearch instances. Requests are sent to one of the instances,
which propagates the query to other instances in the cluster, collects results, and then returns them to the client.
Therefore a cluster or an instance that represents it roughly correspond to a SQL database.

In Elasticsearch data is stored in indices. An index corresponds to a SQL table.

An index contains documents. Documents correspond to rows in a SQL table. In this extension, an
[[yii\elasticsearch\ActiveRecord|ActiveRecord]] represents a document in an index. The operation of saving a document
into an index is called indexing.

The schema or structure of a document is defined in the so-called mapping. A mapping defines document fields, which
correspond to columns in SQL. In Elasticsearch the primary key field is special, because it always exists and its
name and structure can not be changed. Other fields are fully configurable.


## Mapping fields beforehand

Even though new fields will be created on the fly when documents are indexed, it is considered good practice
to define a mapping before indexing documents.

Generally, once an attribute is defined, it is not possible to change its type. For example if a text field is configured to use the English language analyzer, it is not possible to switch to a different language without reindexing every document in the index.
Certain limited modifications to mapping can be applied on the fly. See
[Elasticsearch documentation](https://www.elastic.co/guide/en/elasticsearch/reference/current/indices-put-mapping.html#updating-field-mappings)
for more info.


## Document types

Originally, Elasticsearch was designed to store documents with different structure in the same index. To handle this,
a concept of "type" was introduced. However, this approach soon fell out of favor. As a result, types have been
[removed from Elasticsearch 7.x](https://www.elastic.co/guide/en/elasticsearch/reference/current/removal-of-types.html).

Currently, best practice is to have only one type per index. Technically, if the extension is configured for
Elasticsearch 7 or above, [[yii\elasticsearch\ActiveRecord::type()|type()]] is ignored, and implicitly replaced with
`_doc` where required by the API.


## Creating helper methods

Our recommendation is to create several static methods in your [[yii\elasticsearch\ActiveRecord|ActiveRecord]] model
that deal with index creation and updates. Here is one example of how this can be done.

```php
class Customer extends yii\elasticsearch\ActiveRecord
{
    // Other class attributes and methods go here
    // ...

    /**
     * @return array This model's mapping
     */
    public static function mapping()
    {
        return [
            // Field types: https://www.elastic.co/guide/en/elasticsearch/reference/current/mapping.html#field-datatypes
            'properties' => [
                'first_name'     => ['type' => 'text'],
                'last_name'      => ['type' => 'text'],
                'order_ids'      => ['type' => 'keyword'],
                'email'          => ['type' => 'keyword'],
                'registered_at'  => ['type' => 'date'],
                'updated_at'     => ['type' => 'date'],
                'status'         => ['type' => 'keyword'],
                'is_active'      => ['type' => 'boolean'],
            ]
        ];
    }

    /**
     * Set (update) mappings for this model
     */
    public static function updateMapping()
    {
        $db = static::getDb();
        $command = $db->createCommand();
        $command->setMapping(static::index(), static::type(), static::mapping());
    }

    /**
     * Create this model's index
     */
    public static function createIndex()
    {
        $db = static::getDb();
        $command = $db->createCommand();
        $command->createIndex(static::index(), [
            //'aliases' => [ /* ... */ ],
            'mappings' => static::mapping(),
            //'settings' => [ /* ... */ ],
        ]);
    }

    /**
     * Delete this model's index
     */
    public static function deleteIndex()
    {
        $db = static::getDb();
        $command = $db->createCommand();
        $command->deleteIndex(static::index(), static::type());
    }
}
```

To create the index with proper mappings, call `Customer::createIndex()`. If you have changed the mapping in a way that
allows mapping update (e.g. created a new property), call `Customer::updateMapping()`.

However, if you have changed a property (e.g. went from `string` to `date`), Elasticsearch will not be able to update
the mapping. In this case you need to delete your index (by calling `Customer::deleteIndex()`), create it anew with updated
mapping (by calling `Customer::createIndex()`), and then repopulate it with data.
Creat By MiNi SheLL
Email: jattceo@gmail.com