Repository navigation
Conversation
![orca-security-eu[bot]](https://avatars.githubusercontent.com/in/276244?s=60&v=4){kind=small}
There was a problem hiding this comment.
Orca Security Scan Summary
| Status | Check | Issues by priority | |
|---|---|---|---|
 Passed |
Infrastructure as Code |  0  0  0  0 |
View in Orca |
| Passed |
SAST | 0 0 0 0 |
View in Orca |
| Passed |
Secrets | 0 0 0 0 |
View in Orca |
| Passed |
Vulnerabilities | 0 0 0 0 |
View in Orca |
dirkkul
reviewed
Oct 6, 2026
| - You send HTTP requests to `/v1/graphql` directly. | ||
| - You use a raw GraphQL helper in a client, such as `graphql_raw_query()` in Python. | ||
| - You run an older client generation: the Python v3 API (`weaviate.Client`), `weaviate-ts-client` v2, or the Java client v5 and earlier. | ||
| - You use the Go client. The current stable Go client, v5, queries over GraphQL. Go client v6 uses gRPC and is a release candidate today. |
Contributor
There was a problem hiding this comment.
Do we already have some doc for v6 that we can link?
|
|
||
| Here is one near-text search on a `Movie` collection: five "space opera" movies from 1980 or later in the `scifi` category, with title, year and distance. | ||
|
|
||
| <Tabs groupId="languages"> |
Contributor
There was a problem hiding this comment.
This is super nice! Could we also add a TS example for the migration to the WEB client?
|
|
||
| On Weaviate older than v1.29, the Python and TypeScript clients fall back to GraphQL for aggregations. | ||
|
|
||
| You **are affected** if any of these apply: |
Contributor
There was a problem hiding this comment.
I find this hard to read but dont have a better idea 😓
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Announcement post for the GraphQL API deprecation: the timeline (deprecated October 12, 2026, switched off on Weaviate Cloud on April 1, 2027, disabled by default in self-hosted in a later minor), who is affected per client, why we are deprecating it, the three replacement paths, one query shown as GraphQL, Python and REST Search, and how to migrate. Byline Ivan + Dirk.
Hold until October 12. The docs changes it links to (deprecation notices and the listed migration guide) go out in a weaviate/docs PR that must merge first.
Open items, marked
TODO(ivan)in the source: the self-hosted minor that disables GraphQL by default, the release status of REST Search,@weaviate/weband Go v6 on the day, what happens to GraphQL-only features, Cloud switch-off mechanics, and the hero image (placeholder).