Weaviate Cloud
/v1/objects/{id}/references/{id} endpoint removal
Deprecated, no dateSubscribe to Weaviate CloudShare
Weaviate Cloud deprecated the /v1/objects/{id}/references/{id} endpoint without a shutdown date. Weaviate Cloud announced that the endpoint will be removed in a future version. Requests sent to this route will eventually fail once the removal takes effect.
Calls it hits
/v1/objects/{id}/references/{id}
What to use instead of these calls
Call /v1/objects/{className}/{id}/references/{propertyName} with the object's collection name instead.
In Weaviate Cloud's words
This endpoint is deprecated and will be removed in a future version. Use the `/objects/{className}/{id}/references/{propertyName}` endpoint instead.
Facts
- API
- Weaviate Cloud
*.weaviate.cloud - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Weaviate Cloud's own pages
Questions
When does this change take effect?
Weaviate Cloud deprecated /v1/objects/{id}/references/{id} without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Weaviate Cloud has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Weaviate Cloud 5
-
No date
DELETE /v1/objects/{id}Endpoint removal Deprecated, no date -
No date
GET /v1/objects/{id}Endpoint removal Deprecated, no date -
No date
HEAD /v1/objects/{id}Endpoint removal Deprecated, no date -
No date
PATCH /v1/objects/{id}Endpoint removal Deprecated, no date -
No date
PUT /v1/objects/{id}Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.