US 12,475,092 B2
Systems and methods for lineage-aware data retention
Arnav Jagasia, New York, NY (US); Ashley Meuser, Arlington, VA (US); Mihir Patil, New York, NY (US); Pieris Christofi, London (GB); and Sam Stoll, London (GB)
Assigned to Palantir Technologies Inc., Denver, CO (US)
Filed by Palantir Technologies Inc., Denver, CO (US)
Filed on Jul. 6, 2023, as Appl. No. 18/218,764.
Claims priority of provisional application 63/431,913, filed on Dec. 12, 2022.
Claims priority of provisional application 63/359,044, filed on Jul. 7, 2022.
Prior Publication US 2024/0012797 A1, Jan. 11, 2024
Int. Cl. G06F 16/00 (2019.01); G06F 16/185 (2019.01); G06F 16/21 (2019.01); G06F 16/23 (2019.01)
CPC G06F 16/219 (2019.01) [G06F 16/185 (2019.01); G06F 16/2358 (2019.01); G06F 16/2379 (2019.01)] 20 Claims
OG exemplary drawing
 
1. A method for lineage-aware data retention, the method comprising:
receiving information of a committed transaction, the committed transaction configured to add or change data to a dataset, and the committed transaction being derived from one or more parent transactions;
receiving one or more lineages for the committed transaction;
determining the one or more parent transactions based at least in part on the one or more lineages;
obtaining one or more parent retention dates corresponding to the one or more parent transactions respectively;
assigning a transaction retention date to the committed transaction based at least in part on the one or more parent retention dates corresponding to the one or more parent transactions respectively from which the committed transaction is derived;
receiving an update to a parent retention policy associated with a parent dataset, the updated parent retention policy including an updated parent retention date;
updating the transaction retention date based at least in part on the updated parent retention policy; and
triggering a process to update one or more child transactions associated with one or more child retention dates of the parent dataset, the one or more child transactions including the committed transaction derived from the one or more parent transactions,
wherein the method is implemented by one or more processors.