Weaviate local instance graphql Update "schema is not configured for migration"

Support
1

Hello,
I’m running a local instance of Weaviate using Docker, and everything seems to be functioning well. When I use the Python client to update collections, it works without issues. However, when I attempt to perform updates via GraphQL, I receive the following error: “schema is not configured for migration.”
Could you help me understand why this is happening and how to resolve it?
Thank you!

2

hi @Daniele_Longo !!

Welcome to our community :hugs:

You cannot update objects with graphql. We only expose graphql for reading/querying

For updating objects, you need to use our REST endpoints. For example, this is the one you need to update an object:

Note that while GRAPHQL and REST APIs are convenient, whenever you need more performance, for operations like batch updating, inserting, querying, etc, we suggest using the client, as it leverages GRPC and delivers a lot more performance.

Let me know if this helps!

Thanks!

3

Hi @DudaNogueira ,

Thank you for the answer, isn’t there a console for local instances to query and manipulate data faster, right?

4

hi @Daniele_Longo !

We used to allow our console to add locally hosted clusters, so the browser would connect to your locally hosted Weaviate instance.

Unfortunately we had to limit this feature to our cloud hosted only clusters, as this could potentially be exploited.

However, you can still use any api client, like insomnia or postman to get the same graphql autocomplete functionality.

Here is how It looks like in insomnia:

image
image2200×1218 318 KB

you can also import our openapi specs to use the rest endpoints:

Let me know if this helps!