Sign in
file-search

Overwrite Chunk Metadata in Batches

Overwrite the custom_metadata object on up to 100 chunks in one request. Each item behaves like Overwrite Chunk Metadata. Returns 200 with one result per item, in order. Overwrite is destructive: omitted keys are removed and {} clears the target. Consider copying the collection first. Envelope, partial success, and unknown outcomes are covered in the Batch Metadata & Relations guide.

put/v3/collections/{collection_name}/chunks/metadata/batch

Path parameters

collection_namestring required

Request body

Response

Overwrite Chunk Metadata 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