Model integration messages

Messages on this page are deprecation warnings from the Weaviate Python client, raised when a collection asks for a model integration under a name that has been renamed or retired. The provider is still supported; only the name it is configured under has changed. If your message is not here, the message index lists the other groups.

One of these warnings when you configure a collection. It prints as soon as the configuration object is built, before any request reaches Weaviate, usually together with a generic deprecation notice naming the same replacement:

Dep011: text2vec-palm is deprecated and will be removed in Q2 25. Use text2vec-google instead.
Dep012: multi2vec-palm is deprecated and will be removed in Q2 25. Use multi2vec-google instead.
Dep013: generative.palm is deprecated and will be removed in Q2 25. Use generative.google instead.

Google retired the PaLM name and reorganized these models under Vertex AI and the Gemini API. Weaviate followed in two steps: first renaming the integrations from palm to google, then splitting the Google embedding and generative integrations by service, because Vertex AI and the Gemini API authenticate differently and expose different models. The message was written after the first step, which is why its advice is out of date rather than wrong.

Pick the Google service you actually use, then configure every integration for it. Vertex AI needs the Google Cloud project that owns the model (and, for multimodal, the region); the Gemini API needs neither, and asking for the wrong one means being asked for a project id you do not have.

from weaviate.classes.config import Configure

# Each call creates its own collection: pick the ones you need.

# Text embeddings (was text2vec_palm)
client.collections.create(
    "Article",
    vector_config=Configure.Vectors.text2vec_google_vertex(project_id="my-project"),
)

# Multimodal embeddings (was multi2vec_palm)
client.collections.create(
    "Article",
    vector_config=Configure.Vectors.multi2vec_google(
        project_id="my-project",
        location="us-central1",
        text_fields=["title"],
    ),
)

# Generative search (was generative.palm)
client.collections.create(
    "Article",
    generative_config=Configure.Generative.google_vertex(project_id="my-project"),
)

from weaviate.classes.config import Configure

# Each call creates its own collection: pick the ones you need.

# Text embeddings (was text2vec_palm)
client.collections.create(
    "Article",
    vector_config=Configure.Vectors.text2vec_google_gemini(),
)

# Multimodal embeddings (was multi2vec_palm)
client.collections.create(
    "Article",
    vector_config=Configure.Vectors.multi2vec_google_gemini(
        text_fields=["title"],
    ),
)

# Generative search (was generative.palm)
client.collections.create(
    "Article",
    generative_config=Configure.Generative.google_gemini(),
)

Three things to know when you make the change:

• The collection reports the old name back. Weaviate stores these integrations under their original module names, so a collection configured this way still reads back as text2vec-palm, multi2vec-palm, or generative-palm. That is the storage name, not the name you configure, and it does not need fixing.
• The current forms also use vector_config. That is a separate deprecation, covered in deprecated vector configuration arguments; both land in the same edit because the current builders only exist in the new shape.
• Existing collections are unaffected. The integration is recorded when the collection is created. Change the name in the code that creates new collections; rewriting an existing collection means re-embedding its objects, which is only worth doing if you also want to change the model.

Have a question or feedback? Here's how to reach us.