Collections
Trigger Collection Processing
Changed onProcess data through a collection - works for both bucket-sourced and collection-sourced collections.
**For bucket-sourced collections:**
Creates a batch and answers with its id and a task id, then reads the source
bucket(s), splits a load over 1,000 objects into several batches, and submits
them. Use `include_buckets` to limit which source buckets to process from.
If the buckets hold no matching objects, or a submission is refused, the
batch and the task read FAILED with the reason. The task lists every batch
as `additional_data.trigger.batch_ids` once they are submitted.
**For collection-sourced collections:**
Processes existing documents from upstream collection(s).
Use `include_collections` to limit which source collections to process from.
**Filtering:**
- `source_filters`: Field-level filters using LogicalOperator format
- Example: `{"AND": [{"field": "status", "operator": "eq", "value": "pending"}]}`
- For specific objects: `{"AND": [{"field": "object_id", "operator": "in", "value": ["obj_1", "obj_2"]}]}`
**Returns:**
- batch_id: Track progress via GET /batches/{batch_id}
- task_id: Monitor via GET /tasks/{task_id}
post/v1/collections/{collection_identifier}/trigger
Request
- Base URL: https://api.mixpeek.com
- URL: https://api.mixpeek.com/v1/collections/{collection_identifier}/trigger
- Auth: HTTP bearer and API key in header X-Namespace
Path parameters
collection_identifierstring required
The ID or name of the collection to trigger
Request body
Example request
{
"source_filters": {
"AND": [
{
"field": "name",
"operator": "eq",
"value": "John"
},
{
"field": "age",
"operator": "gte",
"value": 30
}
],
"OR": [
{
"field": "status",
"operator": "eq",
"value": "active"
},
{
"field": "role",
"operator": "eq",
"value": "admin"
}
],
"NOT": [
{
"field": "department",
"operator": "eq",
"value": "HR"
},
{
"field": "location",
"operator": "eq",
"value": "remote"
}
],
"case_sensitive": true
},
"reembed": {
"target_feature_uri": "mixpeek://text_extractor@v1/all_minilm_l6_v2_v1"
}
}Response
Successful Response
Changes
- warning
removed the optional property
from the response with the status - info
added the non-success response with the status
- info
added the non-success response with the status
- info
added the optional property
to the response with the status - info
added the required property
to the response with the status - info
added the required property
to the response with the status
- warning
- info
added the optional property
to the response with the status
- info