Garbage collecting task

Garbage collecting is removing descriptors or events. Heavy requests to internal services are executed with a timeout x 100 compared to the set one.

• It is possible to delete descriptors from luna-faces by specified descriptor_version without accounting

• It is possible to delete face or body descriptors from luna-events by specified descriptor_version and descriptor_type without accounting

• It is possible to delete events by filters along with face and body samples

• It is possible to delete general events by filters along with the images linked from their user-defined fields (face samples, body samples, and image origins, i.e. images uploaded via POST /{api version}/images)

Task allows to remove associated with events images (samples or image_origins) by setting appropriate options for task - remove_samples, remove_image_origins. In case url of the image origin points to external image task tries to remove it by performing DELETE request to the image url.

For general events the targets option lists the paths of the event’s user-defined fields that store links to the images to remove when remove_samples is true. A matched image is removed from the image-store buckets with face samples, body samples, and image origins, so images uploaded via POST /{api version}/images are removed along with the event. A path is dotted for nesting and may use [*] after any segment to reach a field inside every element of an array, at any depth and with any number of [*] (e.g. frames[*].image or store.books[*].chapters[*].url). If the value at a path is a list, all of its elements are processed. Values that are not links to luna-image-store images are silently skipped.

If Luna Image Store is disabled

• the samples removing is disabled

• no subtask/task results will be stored

• after completing the subtask, the task status will be updated as Done and task result id will be None