Properties: delete


Deletes property records that match specified filters.

Delete Markers

Due to the specifics of the underlying storage technology, the records deleted with this method are not instantly removed from the disk.

Instead, the records are masked with a DELETE marker timestamped at the delete request time. The DELETE marker hides all data rows recorded with an earlier timestamp.

The actual deletion from the disk, which removes both the DELETE marker as well as earlier records, occurs in the background as part of a scheduled procedure called major compaction.

Properties that are re-inserted before the major compaction is completed with timestamps earlier than the DELETE marker is not visible.

To identify pending DELETE markers for a given type and entity, run:

echo "scan 'atsd_properties', {'LIMIT' => 3, RAW => true, FILTER => \"PrefixFilter('\\"prop_type\\":\\"entity_name\\"')\"}" | /opt/atsd/hbase/bin/hbase shell

The same behavior applies to properties deleted when the entire entity is removed, except in this case the DELETE marker is timestamped with the Long.MAX_VALUE-1 time of 9223372036854775806.

To remove these markers, run major compaction on the atsd_properties table ahead of schedule.

echo "major_compact 'atsd_properties'" | /opt/atsd/hbase/bin/hbase shell


Method Path Content-Type Header
POST /api/v1/properties/delete application/json




An array of objects containing fields for filtering records for deletion.

Field Type Description
type string [Required] Property type name.
This method does not allow removal of the reserved $entity_tags type.
entity string [Required] Entity name.
Set entity to wildcard * to delete records for all entities.
startDate string [Required] ISO 8601 date or calendar keyword.
Delete records updated at or after the specified time.
endDate string [Required] ISO 8601 date or calendar keyword.
Delete records updated before the specified time.
key object Object with name=value fields, for example {"file_system": "/"}.
Deletes records with exact or partial key fields based on the exactMatch parameter below.
exactMatch boolean If exactMatch is true, only one record with exactly the same key as in the request is deleted.
If false, all records with key that contains fields in the request key (but can include other fields) are deleted.
If exactMatch is false and no key is specified, all records for the specified type and entity are deleted.
Default: true.
  • Key and tag names are case-insensitive.
  • Key and tag values are case-sensitive.






Key Match Example

Assuming property records A,B,C, and D exist:

| record | type   | entity | key-1 | key-2 |
| A      | type-1 | e-1    | val-1 | val-2 |
| B      | type-1 | e-2    | val-1 |       |
| C      | type-1 | e-3    |       | VAL-3 |
| D      | type-1 | e-4    |       |       |

The table below illustrates which records are deleted (the result column) for the corresponding exactMatch and key parameters on the left.

| exactMatch | key                     | result  |
| true       |                         | D       |
| false      |                         | A;B;C;D |
| true       | key-1=val-1             | B       |
| false      | key-1=val-1             | A;B     |
| true       | key-1=val-1;key-2=val-2 | A       |
| false      | key-1=val-1;key-2=val-2 | A       |
| false      | key-2=val-3             |         |
| false      | key-2=VAL-3             | C       |




POST /api/v1/properties/delete


    "exactMatch": false


curl https://atsd_hostname:8443/api/v1/properties/delete \
  --insecure --include --user {username}:{password} \
  --header "Content-Type: application/json" \
  --data '[{ "type":"disk", "entity":"nurswgvml007", "key":{"file_system":"/","name":"sda1"} }]'