# US 2021/0232604 A1 · Capturing data lake changes

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2021/0232604 A1
- Document ID: US20210232604A1
- Status: Published application
- Kind: A1
- Application number: 16/775,306
- Filed: 2020-01-29
- Published: 2021-07-29
- Earliest claimed: 2020-01-29
- Assignees: salesforce.com, inc.
- Applicants: Salesforce.com, Inc.
- Inventors: Shreedhar Sundaram; Mahalaxmi Sanathkumar; Aaron Zhang; Parin Kenia; Violet Gong; Priya Sethuraman; Zhidong Ke; Kevin Terusak
- Web page: https://patentgrep.com/patent/US20210232604A1

## CPC

- G06F 16/283: {Multi-dimensional databases or data warehouses, e.g. MOLAP or ROLAP}
- G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors
- G06F 16/2322: {using timestamps}
- G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)}
- G06F 16/24534: {Query rewriting; Transformation}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A request may be received to transform records in a data lake that match one or more query criteria. Data lake records that match the criteria may be retrieved. The retrieved records may include two data lake records associated with the same data lake record identifier. A transformed record may be generated based on time stamps associated with the retrieved records.

## Claims

### Claim 1

A computer-implemented method comprising:
receiving a request to transform records in a data lake that match one or more query criteria;
retrieving from the data lake a plurality of data lake records that match the one or more query criteria, the plurality of data lake records including a first data lake record and a second data lake record, the first data lake record being associated with a designated data lake record identifier and a first timestamp identifying when the first data lake record was created, the second data lake record being associated with the designated data lake record identifier and a second timestamp identifying when the second data lake record was created;
based on a comparison of the first timestamp to the second timestamp, generating a transformed data lake record based on the first data lake record; and
transmitting the transformed data lake record to a downstream data service.

### Claim 2 (depends on 1)

The computer-implemented method recited in claim 1, wherein the comparison comprises determining that the first timestamp precedes the second timestamp.

### Claim 3 (depends on 1)

The computer-implemented method recited in claim 1, wherein the designated data lake record identifier is associated with a third data lake record corresponding with an update request.

### Claim 4 (depends on 3)

The computer-implemented method recited in claim 3, wherein the third data lake record is associated with a third timestamp that precedes the second timestamp, and wherein the first timestamp precedes the third timestamp.

### Claim 5 (depends on 1)

The computer-implemented method recited in claim 1, wherein the designated data lake record identifier is associated with a third request to delete the first data lake record, and wherein the third data lake record is associated with a third timestamp.

### Claim 6 (depends on 5)

The computer-implemented method recited in claim 5, wherein the first data lake record is flagged for deletion after a designated period of time has elapsed after the third timestamp.

### Claim 7 (depends on 1)

The computer-implemented method recited in claim 1, wherein a designated one of the data lake partition identifiers is associated with a pointer to a file in the data lake.

### Claim 8 (depends on 7)

The computer-implemented method recited in claim 7, wherein the pointer to the file is a partition key in a Delta Lake change log table.

### Claim 9 (depends on 1)

The computer-implemented method recited in claim 1, wherein the pointer to the file is a URI independent of a file system underlying the data lake.

### Claim 10 (depends on 1)

The computer-implemented method recited in claim 1, wherein the data lake records are stored in one or more third-party cloud computing storage system.

### Claim 11 (depends on 1)

The computer-implemented method recited in claim 1, wherein the data lake is accessible via an on-demand computing services environment providing computing services to a plurality of organizations via the internet.

### Claim 12 (depends on 11)

The computer-implemented method recited in claim 11, wherein the computing services environment includes a multitenant database that stores information associated with the plurality of organizations.

### Claim 13

A computing system implemented in a cloud computing environment, the computing system configured to perform a method comprising:
receiving a request to transform records in a data lake that match one or more query criteria;
retrieving from the data lake a plurality of data lake records that match the one or more query criteria, the plurality of data lake records including a first data lake record and a second data lake record, the first data lake record being associated with a designated data lake record identifier and a first timestamp identifying when the first data lake record was created, the second data lake record being associated with the designated data lake record identifier and a second timestamp identifying when the second data lake record was created;
based on a comparison of the first timestamp to the second timestamp, generating a transformed data lake record based on the first data lake record; and
transmitting the transformed data lake record to a downstream data service.

### Claim 14 (depends on 13)

The computing system implemented recited in claim 13, wherein the comparison comprises determining that the first timestamp precedes the second timestamp.

### Claim 15 (depends on 13)

The computing system implemented recited in claim 13, wherein the designated data lake record identifier is associated with a third data lake record corresponding with an update request.

### Claim 16 (depends on 15)

The computing system implemented recited in claim 15, wherein the third data lake record is associated with a third timestamp that precedes the second timestamp, and wherein the first timestamp precedes the third timestamp.

### Claim 17 (depends on 13)

The computer-implemented method recited in claim 13, wherein the designated data lake record identifier is associated with a third request to delete the first data lake record, and wherein the third data lake record is associated with a third timestamp, and wherein the first data lake record is flagged for deletion after a designated period of time has elapsed after the third timestamp.

### Claim 18

One or more non-transitory machine-readable media having instructions stored thereon for performing a method, the method comprising:
receiving a request to transform records in a data lake that match one or more query criteria;
retrieving from the data lake a plurality of data lake records that match the one or more query criteria, the plurality of data lake records including a first data lake record and a second data lake record, the first data lake record being associated with a designated data lake record identifier and a first timestamp identifying when the first data lake record was created, the second data lake record being associated with the designated data lake record identifier and a second timestamp identifying when the second data lake record was created;
based on a comparison of the first timestamp to the second timestamp, generating a transformed data lake record based on the first data lake record; and
transmitting the transformed data lake record to a downstream data service.

### Claim 19 (depends on 18)

The one or more non-transitory machine-readable media recited in claim 18, wherein the comparison comprises determining that the first timestamp precedes the second timestamp.

### Claim 20 (depends on 18)

The one or more non-transitory machine-readable media recited in claim 18, wherein the designated data lake record identifier is associated with a third data lake record corresponding with an update request.
