You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idempotent nature of PUT is sometimes confusing for users. In order to change one prop of a schema, the user needs to first retrieve the schema, make an alteration, then send the schema back to Weaviate. That is correct usage of the PUT verb:
A successful PUT of a given representation would suggest that a subsequent GET on that same target resource will result in an equivalent representation being sent in a 200 (OK) response. Source: RFC7231
However, it is not the most comfortable way to update a schema. Instead, we could also allow a partial update using PATCH. In this case, the user would only send the property they want to be updated and Weaviate would merge the update with the existing schema.
The text was updated successfully, but these errors were encountered:
The idempotent nature of
PUT
is sometimes confusing for users. In order to change one prop of a schema, the user needs to first retrieve the schema, make an alteration, then send the schema back to Weaviate. That is correct usage of the PUT verb:However, it is not the most comfortable way to update a schema. Instead, we could also allow a partial update using
PATCH
. In this case, the user would only send the property they want to be updated and Weaviate would merge the update with the existing schema.The text was updated successfully, but these errors were encountered: