![]() purge command triggers this process, which takes a few days to complete. These timelines are set to follow data privacy requirements. This phase is done at least five days after the completion of the previous phase, but no longer than 30 days after the initial command. Work back all storage artifacts that may have the "poison" data, and delete them from storage. The duration of phase 2 can vary between a few seconds to many hours. The spare capacity it has for purge operations.Record distribution across the data extents in the cluster.The number of records that must be purged.The duration of the purge soft delete phase depends on the following parameters: If new data isn't being ingested into the table, then by the end of this phase, queries will no longer return data for which the predicate returns true. The reingested version shouldn't have the records for which the predicate returns true. Replace each data extent in the table (identified in step (1)) with a reingested version. The extents identified are those having one or more records for which the predicate returns true. Kusto scans the table looking to identify data extents that would participate in the data purge. ![]() Give an input with an Azure Data Explorer table name and a per-record predicate, indicating which records to delete. The process of selectively purging data from Azure Data Explorer happens in the following steps: Instead, send a single command whose predicate includes all user identities that require purging. ![]() Don't issue multiple commands with unique user identity predicates. purge commands to 1-2 commands per table per day.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |