# Incorrect vectorizer set in collection schema (text2vec-google vs text2vec-palm)

**URL:** <https://forum.weaviate.io/t/incorrect-vectorizer-set-in-collection-schema-text2vec-google-vs-text2vec-palm/21980>\
**Category:** General\
**Created:** [September 18, 2025, 11:37am UTC](https://forum.weaviate.io/t/incorrect-vectorizer-set-in-collection-schema-text2vec-google-vs-text2vec-palm/21980 "2025-09-18T11:37:21Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Muhammad\_Ashir](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/muhammad_ashir/32/2644_2.png) [@Muhammad\_Ashir](https://forum.weaviate.io/u/Muhammad_Ashir)\
**Post date:** [September 18, 2025, 11:37am UTC](https://forum.weaviate.io/t/incorrect-vectorizer-set-in-collection-schema-text2vec-google-vs-text2vec-palm/21980/1 "2025-09-18T11:37:21Z")

</div>

Hi everyone,

I’m running into an issue where my collection is being created with `text2vec-palm` as the vectorizer, even though I’ve set everything to use **text2vec-google** (Gemini embeddings).

`vectorizer_config = wvc.config.Configure.Vectorizer.text2vec_google(`  
`project_id=“myid”,`  
`)`

Docker Compose setup

```auto
volumes:
  - weaviate_gemini:/var/lib/weaviate
  - ./credentials/google_credentials.json:/etc/weaviate/google_credentials.json:ro
restart: on-failure:0
environment:
  QUERY_DEFAULTS_LIMIT: 5000
  AUTHENTICATION_ANONYMOUS_ACCESS_ENABLED: "true"
  PERSISTENCE_DATA_PATH: "/var/lib/weaviate"
  ENABLE_API_BASED_MODULES: true
  DEFAULT_VECTORIZER_MODULE: text2vec-google
  ENABLE_MODULES: text2vec-google
  CLUSTER_HOSTNAME: "node1"
  MODULES_CLIENT_TIMEOUT: "1h"
  USE_GOOGLE_AUTH: "true"
  GOOGLE_APPLICATION_CREDENTIALS: "/etc/weaviate/google_credentials.json"

```

### Actual schema being created

```auto
{
  "class": "Collection_ddd",
  "invertedIndexConfig": {
    "bm25": { "b": 0.75, "k1": 1.2 },
    "cleanupIntervalSeconds": 60,
    "stopwords": { "preset": "en" }
  },
  "moduleConfig": {
    "text2vec-palm": {
      "modelId": "gemini-embedding-001",
      "projectId": " ***removed***",
      "vectorizeClassName": true
    }
  },
  "properties": [
    {
      "name": "fileId",
      "dataType": ["text"],
      "moduleConfig": {
        "text2vec-palm": { "skip": true, "vectorizePropertyName": true }
      }
    },
    {
      "name": "fileContent",
      "dataType": ["text"],
      "moduleConfig": {
        "text2vec-palm": { "skip": false, "vectorizePropertyName": true }
      }
    }
  ],
  "vectorIndexConfig": { "distance": "cosine" },
  "vectorIndexType": "hnsw",
  "vectorizer": "text2vec-palm"
}

```

Even though I’m using `text2vec-google` in both my Docker config and collection creation code, the schema always ends up with **`text2vec-palm`** as the vectorizer.

When I try to query, I get this error:

**no vectorizer module “text2vec-palm” is configured**

### Versions

- **Weaviate server** : `1.27.4`

- **Weaviate Python client** : `4.10.1`

---

<div class="post-metadata">

**Author:** ![Shahin](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/shahin/32/7944_2.png) [@Shahin](https://forum.weaviate.io/u/Shahin)\
**Post date:** [September 18, 2025, 11:51am UTC](https://forum.weaviate.io/t/incorrect-vectorizer-set-in-collection-schema-text2vec-google-vs-text2vec-palm/21980/2 "2025-09-18T11:51:18Z")

</div>

Hey @Muhammad_Ashir ,

It’s just module name change text2vec-google was called text2vec-palm in Weaviate versions prior to v1.27

> **[Text Embeddings | Weaviate Documentation](https://docs.weaviate.io/weaviate/model-providers/google/embeddings#weaviate-configuration)**
>
> Weaviate's integration with Google Gemini API and Google Vertex AI APIs allows you to access their models' capabilities directly from Weaviate.

Also It would be great if you upgrade your Weaviate to latest as you are way outdated - we are almost releasing 1.33

Best regards,

Mohamed Shahin  
Weaviate Support Engineer  
(Ireland, UTC±00:00/+01:00)
