# Unique vs Multiple dense vectors

**URL:** <https://discuss.elastic.co/t/unique-vs-multiple-dense-vectors/385710>\
**Category:** Elasticsearch\
**Tags:** vector-search\
**Created:** [March 31, 2026, 12:05pm UTC](https://discuss.elastic.co/t/unique-vs-multiple-dense-vectors/385710 "2026-03-31T12:05:43Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![cilasmarques](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cilasmarques/32/146350_2.png) [@cilasmarques](https://discuss.elastic.co/u/cilasmarques)\
**Post date:** [March 31, 2026, 12:05pm UTC](https://discuss.elastic.co/t/unique-vs-multiple-dense-vectors/385710/1 "2026-03-31T12:05:43Z")

</div>

Hi there!

I'm adding semantic search to my site's search functionality. I use Elasticsearch and my index is structured as follows:

```auto
"title":{
  "type":"text",
  "analyzer":"general_analyzer",
  "fields": {
      "spell": {
         "type": "text",
         "analyzer": "spell_analyzer",
         "similarity": "BM25"
      }
  }
},
"description":{
  "type":"text",
  "analyzer":"general_analyzer"
}

```

I'd like to understand the best way to proceed: whether to add a `single dense_vector` (combining title + description) or to have `multiple dense_vectors` (one for each field). Why?

Note: My titles are around 60 characters / 10 words, and my descriptions are around 670 characters / 90 words.

Thank you for your attention!  
[]s

---

<div class="post-metadata">

**Author:** ![john-wagster](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/john-wagster/32/139021_2.png) [@john-wagster](https://discuss.elastic.co/u/john-wagster)\
**Post date:** [April 1, 2026, 12:58am UTC](https://discuss.elastic.co/t/unique-vs-multiple-dense-vectors/385710/2 "2026-04-01T00:58:30Z")

</div>

I would start with a single `dense_vector` field; here’s the docs if it would help: [Dense vector field type | Elasticsearch Reference](https://www.elastic.co/docs/reference/elasticsearch/mapping-reference/dense-vector)

I’d probably structure the text as something like “Title: TITLE Description: DESCRIPTION” and then embed it. LLMs like having as much context as possible usually and your use-case doesn’t seem like too much context for most LLMs to me right off though your mileage will vary depending on how you do embed it.

Ultimately whether using a single field is sufficient will depend on how the data gets embedded in the space and how you want to query it. But one field is the simplest and least expensive way and will probably give you the results you want. Let me know how it goes.