User-defined loading of data onto a database

Patent metadata

Field	Value
Publication number	US-10474658-B2
Application number	US-201214405563-A
Country	US
Kind code	B2
Filing date	Jun 4, 2012
Priority date	Jun 4, 2012
Publication date	Nov 12, 2019
Grant date	Nov 12, 2019

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.

First claim

What is claimed is:

1. A method for managing loading of data from a source onto a database, said method comprising:
providing, by a processor, an interface through which a user is to define a logic to control the loading of the data onto the database;
receiving, by the processor, the user-defined logic via the interface, wherein the user-defined logic comprises a user-defined location identification of the source, a user-defined filter to be applied on the data, a user-defined parsing operation to be executed on the data to convert the data into a format compatible with the database, and a user-defined policy that defines that the data is to be retrieved from the source during a query time;
determining, by the processor, that the query time has been reached;
based on a determination that the query time has been reached, converting, by the processor, the data into a format compatible with the database according to the received user-defined logic;
determining, by the processor, a data loading operation that optimizes loading of the data from the source to the database; and
loading, by the processor, the converted data onto the database according to the determined data loading operation.

2. 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.

3. 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.

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

5. The method according to claim 1 , wherein converting the data into a format compatible with the database according to the received user-defined logic further comprises executing the user-defined logic as part of a pre-configured data-load stack.

6. The method according to claim 1 , further comprising:
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 by executing the parsing operation; and
wherein loading the converted data includes loading the parsed data onto the database.

7. 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.

8. The method according to claim 1 , further comprising executing 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 executing the user-defined logic further comprises executing the user-defined logic on a plurality of systems in the distributed database system while executing a database optimization operation.

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

10. An apparatus for managing loading of data from a source onto a database, the apparatus comprising:
a processor; and
a memory on which is stored machine readable instructions that when executed by the processor cause the processor to:
provide an interface through which a user is to define functions to control the loading of the data onto the database;
receive the user-defined functions via the interface, wherein the user-defined functions comprise a user-defined parsing operation to be executed on the data to convert the data into a format compatible with the database and a user-defined policy that defines that the data is to be retrieved from the source during a query time;
determine that the query time has been reached;
based on a determination that the query time has been reached, convert the data into a format compatible with the database according to the received user-defined functions;
determine a data loading operation that optimizes loading of the data from the source to the database; and
load the converted data onto the database according to the determined data loading operation.

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

12. The apparatus according to claim 10 , wherein the user-defined functions further comprise a user-defined policy that defines at least one 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 instructions are further to cause the processor to:
retrieve the data from the source using a user-defined location identification of the source;
filter the data using a user-defined filter;
parse the data by executing the parsing operation; and
load the parsed data onto the database.

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

14. The apparatus of claim 10 , wherein the user-defined functions further comprise at least one a user-defined location identification of the source or a user-defined filter to be applied on the data.

15. The apparatus of claim 14 , wherein the user-defined filter to be applied on the data is to at least one of: decompress, compress, or convert the data.

16. A non-transitory computer readable storage medium on which is stored machine readable instructions that when executed by a processor, cause the processor to:
provide an interface through which a user is to define code to control loading of data onto a database, wherein the user-defined code includes a user-defined location identification of the source, a user-defined policy that defines that the data is to be retrieved from the source during a query time;
receive the user-defined code;
determine that the query time has been reached;
based on a determination that the query time has been reached, execute the user-defined code to transform the data into a format that is compatible with the database;
determine a data loading operation that optimizes loading of the data from the source to the database; and
execute the user-defined code to load the transformed data onto the database according to the determined data loading operation.

17. The non-transitory computer readable storage medium of claim 16 , wherein the user-defined code further includes a user-defined filter to be applied on the data, instructions for management of the data loaded onto the database, or a parsing operation to be executed on the data to convert the data into a format that is compatible with the database.

18. The non-transitory computer readable storage medium of claim 17 , wherein the user-defined filter to be applied on the data is to at least one of: decompress, compress, or convert the data.

19. The non-transitory computer readable storage medium of claim 17 , wherein the instructions are further to cause the processor to execute the user-defined logic in a system that manages the database, wherein the system that manages the database comprises a distributed database system.

20. The non-transitory computer readable storage medium of claim 17 , wherein the instructions are further to cause the processor to retrieve, filter, and parse the data, an

Assignees

• Seering Adam
• Venkatesh Rajat
• Bear Charles Edward
• Lawande Shilpa
• Lamb Andrew Allinson
• Micro Focus Llc

Inventors

• Seering Adam
• Venkatesh Rajat
• Bear Charles Edward
• Lawande Shilpa
• Lamb Andrew Allinson

Classifications

• G06F40/205

  Parsing · CPC title

• G06F16/254

  Extract, transform and load [ETL] procedures, e.g. ETL data flows in data warehouses · CPC title

• G06F16/258 Primary

  Data format conversion from or to a database · CPC title

• G06F16/214

  Database migration support · CPC title

• G06F16/2291 Primary

  User-Defined Types; Storage management thereof · CPC title