# ftsIndexes

{% hint style="danger" %}
#### This configuration option has been deprecated in API version v2.0.0.

This version deprecated the pg\_trgm Support Optional feature. Because this configuration option was used for pg\_trgm Support, it has been deprecated as well. Until further notice, this configuration option will be used for pg\_trgm Support but will not receive any technical support.
{% endhint %}

{% hint style="info" %}
#### Experimental Feature

This configuration entry is related to an Experimental (Optional) feature called pg\_trgm Support. Before you start to configure this section, make sure to read the page specific for this feature (accessible [here](../../optional-features/schema-improvements/pgtrgm-support)) and [this](../../concepts/experimental-features) page that explains how to enable Experimental Features.
{% endhint %}

### Type: [Map](../types-and-objects/map)<[FileModel](../types-and-objects/file-model), [IndexData](../types-and-objects/index-data)>

<details>

<summary>Versioning History</summary>

**API Version v1.3.0** - Introduced `ftsIndexes` configuration option.

**API Version v2.0.0** - Removed `ftsIndexes` configuration option.

</details>

This object's entries are a key-value pair. When the migrations are generated, Prisma Util will change them to create indexes for these models. To configure your full-text search indexes, add the following line to your exported configuration object:

{% code title="prisma-util.config.mjs" %}
```javascript
export default {
    // Other configuration lines
    ftsIndexes: {
        "models/post/Post.prisma": {
            type: "Gin",
            indexes: [{
                language: "english",
                field: "title",
                weight: "A"
            }]
        }
    }
};
```
{% endcode %}
