# US 2015/0178342 A1 · User-defined loading of data onto a database

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

- Number: US 2015/0178342 A1
- Document ID: US20150178342A1
- Status: Published application
- Kind: A1
- Application number: 14/405,563
- Filed: 2012-06-04
- Published: 2015-06-25
- Earliest claimed: 2012-06-04
- Assignees: Micro Focus LLC
- Inventors: Adam Seering; Rajat Venkatesh; Charles Edward Bear; Shipa Lawande; Andrew Allinson Lamb
- Web page: https://patentgrep.com/patent/US20150178342A1

## CPC

- G06F 16/2291: {User-Defined Types; Storage management thereof}
- G06F 7/36: Combined merging and sorting
- G06F 16/214: {Database migration support}
- G06F 16/254: {Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses}
- G06F 16/258: {Data format conversion from or to a database}
- G06F 40/205: Parsing
- H04L 67/565: Conversion or adaptation of application format or content (adding application control or application functional data H04L67/561)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

As part of managing the loading of data from a source onto a database, according to an example, an interface through which a user is to define logic related to the loading of the data onto the database is provided. The user-defined logic pertains to at least one of a user-defined location identification of the source, a user-defined filter to be applied on the data, and a user-defined parsing operation to be performed on the data to convert the data into an appropriate format for the database. In addition, the user-defined logic is received and the user-defined logic is implemented to load the data onto the database.

## Claims

### Claim 1

A method for managing loading of data from a source onto a database, said method comprising:
providing an interface through which a user is to define logic related to the loading of the data onto the database, wherein the user-defined logic pertains to a user-defined location identification of the source, a user-defined filter to be applied on the data, and a parsing operation to be performed on the data to convert the data into an appropriate format for the database;
receiving the user-defined logic; and
implementing, by a processor, the user-defined logic to load the data onto the database.

### Claim 2 (depends on 1)

The method according to claim 1, wherein providing the interface further comprises providing the interface through which the user is to define the logic by programming the logic, said method further comprising:
storing the programmed logic in a library.

### Claim 3 (depends on 1)

The method according to claim 1, wherein providing the interface further comprises providing access to a library on which is stored previously defined logic through the interface, and wherein receiving the user-defined logic further comprises receiving previously stored logic from the library.

### Claim 4 (depends on 1)

The method according claim 1, wherein the user-defined filter to be applied on the data is to at least one of uncompress, compress, and convert the data.

### Claim 5 (depends on 1)

The method according to claim 1, wherein implementing the user-defined logic further comprises implementing the user-defined logic as part of a pre-configured data-load stack.

### Claim 6 (depends on 1)

The method according to claim 1, wherein implementing the user-defined logic further comprises:
retrieving the data from the source using the user-defined location identification of the source;
filtering the data using the user-defined filter;
parsing the data through performance of the parsing operation; and
loading the parsed data onto the database.

### Claim 7 (depends on 6)

The method according to claim 6, wherein retrieving, filtering, parsing, and loading the parsed data further comprises retrieving, filtering, parsing, and loading the parsed data as the data is streamed from the source.

### Claim 8 (depends on 1)

The method according to claim 1, wherein the user-defined logic further pertains to a user-defined policy that defines a condition to be met prior to the data being retrieved from the source.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the user-defined logic further pertains to a user-defined policy that defines how data loaded onto the database is to be managed.

### Claim 10 (depends on 1)

The method according to claim 1, wherein implementing the user-defined logic further comprises implementing the user-defined logic in a system that manages the database, wherein the system that manages the database comprises a distributed database system and wherein implementing the user-defined logic further comprises implementing the user-defined logic on a plurality of the systems in the distributed database system while implementing a database optimization operation.

### Claim 11

An apparatus for managing loading of data from a source onto a database, said apparatus comprising:
at least one module to,
provide an interface through which a user is to define functions related to the loading of the data onto the database, wherein the user-defined functions pertain to a user-defined location identification of the source, a user-defined filter to be applied on the data, and a parsing operation to be performed on the data to convert the data into a format that is compatible with the database;
receive the user-defined functions; and
implement the user-defined functions to load the data onto the database;
a processor to implement the at least one module.

### Claim 12 (depends on 11)

The apparatus according to claim 11, wherein the user-defined logic further pertains to a user-defined policy that defines at least one of a condition to be met prior to the data being retrieved from the source and management of the data loaded onto the database, and wherein the at least one module is further to:
retrieve the data from the source using the user-defined location identification of the source according to the user-defined policy;
filter the data using the user-defined filter;
parse the data through performance of the parsing operation; and
load the parsed data onto the database.

### Claim 13 (depends on 11)

The apparatus according to claim 11, wherein the apparatus comprises a database management apparatus.

### Claim 14 (depends on 11)

The apparatus according to claim 11, wherein the database is a relational database.

### Claim 15

A non-transitory computer readable storage medium on which is stored machine readable instructions that when executed by a processor, implement a method for managing loading of data from a source onto a database, said machine readable instructions comprising code to:
provide an interface through which a user is to define code related to the loading of the data onto the database, wherein the user-defined code pertains to a user-defined location identification of the source, a user-defined filter to be applied on the data, a user-defined policy that defines at least one of a condition to be met prior to the data being retrieved from the source and management of the data loaded onto the database, and a parsing operation to be performed on the data to convert the data into format that is compatible with the database;
receive the user-defined code;
implement the user-defined code to transform the data into a format suitable for loading the data onto the database; and
implementing the user-defined code to load the data onto the database.
