# Multiple Custom Embedding/Vectors

**URL:** <https://forum.weaviate.io/t/multiple-custom-embedding-vectors/827>\
**Category:** Support\
**Created:** [October 15, 2023, 7:35am UTC](https://forum.weaviate.io/t/multiple-custom-embedding-vectors/827 "2023-10-15T07:35:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shaimaa.Sabry](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/shaimaa.sabry/32/572_2.png) [@Shaimaa.Sabry](https://forum.weaviate.io/u/Shaimaa.Sabry)\
**Post date:** [October 15, 2023, 7:35am UTC](https://forum.weaviate.io/t/multiple-custom-embedding-vectors/827/1 "2023-10-15T07:35:46Z")

</div>

I know how to store and query one custom vector:

```auto
with client.batch as batch:
                properties = {"name": entity.name}
                batch.add_data_object(
                    properties, 
                    "test_class", 
                    vector=embed(entity.name)
                )

response = client.query.get(
                "test_class", 
                ["name"]
            ).with_near_vector(
                {
                    "vector": embed(query),
                    "certainty": 0.7
                }
            ) \
            .with_limit(2) \
            .do()

```

However, I need to store and query multiple custom vectors not just one. How can I achieve my goal?

---

<div class="post-metadata">

**Author:** ![hsm207](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/hsm207/32/19_2.png) [@hsm207](https://forum.weaviate.io/u/hsm207)\
**Post date:** [October 15, 2023, 8:06am UTC](https://forum.weaviate.io/t/multiple-custom-embedding-vectors/827/2 "2023-10-15T08:06:56Z")

</div>

At the moment, weaviate only supports one vector per object. However, support for multiple vector per objects is planned for version 1.23. Please have a look at this issue and let us know if it aligns with your use case:

> <https://github.com/weaviate/weaviate/issues/2465>
>
> Right now an object is associated with 0..1 vectors. But for some use cases it w…ould be nice to have multiple vector properties. For example, we could introduce the \`dataType\` \`vector\` and then users could add arbitrary vectors, such as:
> 
> \`\`\`yaml
> properties:
> \- name: title
> dataType: \['text'\]
> \- name: title\_vector
> dataType: \['vector'\]
> \`\`\`
> 
> Note: It would probably make sense to name the type after the vector data type, e.g. instead of just having \`vector\`, we could have specific vectors, such as \`vectorFloat32\`, \`vectorFloat16\`, \`vectorInt8\`, \`vectorBinary\`, etc.