Sign in
file-search

Create or Update Chunk Relations in Batches

Create or update up to 100 chunk relations in one request. A relation is identified by its source chunk, target chunk, and relation_type. When no relation with that identity exists, one is created and the item returns 201. When exactly one exists, it keeps its relation_id and its entire metadata object is replaced: keys omitted from the item are removed, and {} clears the metadata. Relations not named in the request are left unchanged. This differs from Create Chunk Relation, which always creates and can therefore produce duplicate relations; when more than one existing relation matches an item's identity, the batch changes nothing and fails that item with 409 relation_identity_ambiguous. Returns 200 with one result per item, in order. Envelope, partial success, and unknown outcomes are covered in the Batch Metadata & Relations guide.

put/v3/collections/{collection_name}/relations/batch

Path parameters

collection_namestring required

Request body

Response

Create or Update Chunk Relations in Batches response.

Changes

Changed in 3 of the 13 revisions of this API.1314

  • 61a9364ad042312See the full diff
    • ●

      removed the optional property from the response with the status

      response-optional-property-removed

    • ●

      removed the optional property from the response with the status

      response-optional-property-removed

    • ●

      removed the optional property from the response with the status

      response-optional-property-removed

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the optional property to the response with the status

      response-optional-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    • ○

      added the required property to the response with the status

      response-required-property-added

    This revision also has 10 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • 6ed36830de7111See the full diff
    • ▲

      added subschema #2 subschema #3 to the / response property oneOf list for the response status

      response-property-one-of-added

    • ○

      removed subschema #2 subschema #3 from the / response property oneOf list for the response status

      response-property-one-of-removed

    This revision also has 3 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog

  • cce5328224151See the full diff
    • ○

      endpoint added

      endpoint-added

    This revision also has 2 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog