# Enrich source index compression

**URL:** <https://discuss.elastic.co/t/enrich-source-index-compression/358058>\
**Category:** Elasticsearch\
**Created:** [April 23, 2024, 8:29pm UTC](https://discuss.elastic.co/t/enrich-source-index-compression/358058 "2024-04-23T20:29:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![cvarano](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cvarano/32/122082_2.png) [@cvarano](https://discuss.elastic.co/u/cvarano)\
**Post date:** [April 23, 2024, 8:29pm UTC](https://discuss.elastic.co/t/enrich-source-index-compression/358058/1 "2024-04-23T20:29:59Z")

</div>

I have a very large source index for an enrich policy that stores two `sparse_vector` fields, which is almost 500gb on disk (no replicas).

Here's the source index mappings:

```auto
{
  "mappings": {
    "dynamic_templates": [],
    "properties": {
      "embedding_one": {
        "type": "sparse_vector"
      },
      "embedding_two": {
        "type": "sparse_vector"
      }
      "doc_id": {
        "type": "keyword"
      },
      "is_truncated": {
        "type": "boolean"
      }
    }
  }
}

```

And here's the enrich policy:

```auto
{
  "match": {
    "indices": "source_index_1",
    "match_field": "doc_id",
    "enrich_fields": ["embedding_one", "embedding_two"]
  }
}

```

What can I do from [Tune for Disk Usage](https://www.elastic.co/guide/en/elasticsearch/reference/current/tune-for-disk-usage.html) to the source index? In other words, what features does an enrich policy not require of its source index?

For example, does the enrich policy require the source index to keep \_source enabled? Can I set `"index": false` on the sparse vectors? What about on the "doc\_id"?