System and Method Involving Resource Description Framework Distributed Database Management System and/or Related Aspects

• US 20150234884A1
• Filed: 11/08/2013
• Published: 08/20/2015
• Est. Priority Date: 11/08/2012
• Status: Abandoned Application

• Current Assignee: Sparkledb As
• Original Assignee: Sparkledb As
• Inventors: Henriksen, Inge Eivind
• Application Number:
  US14/232,243
• Publication Number:
  US 20150234884A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 16/21 Design, administration or maintenance of databases
• CPC Class Codes: G06F 16/2336 Pessimistic concurrency control approaches, e.g. locking or multiple versions without time stamps
• CPC Class Codes: G06F 16/2455 Query execution
• CPC Class Codes: G06F 16/275 Synchronous replication
• CPC Class Codes: G06F 16/28 Databases characterised by their database models, e.g. relational or object models
• CPC Class Codes: G06F 16/951 Indexing; Web crawling techniques

Abstract

Implementations herein pertain to database management, such as systems and methods involving Resource Description Framework (RDF) Distributed Database Management Systems (DDMS) and/or related aspects.

Claims

1. A method for performing database management utilizing distributed Resource Description Framework (RDF) repositories, the method comprising

providing transaction management via a concurrency controller;

processing data between the concurrency controller and storage via a database engine, the storage comprising a first storage and a second storage; and

performing query processing via a query processor connected with the database engine.

4. The method of claim 1, wherein the HTTP endpoint supports at least one of SPARQL 1.1 protocol, HTTP 1.1 network protocol, and HTTP 2.0 network protocol.

11. The method of claim 1 further comprising utilizing a master database node comprising:

a concurrency controller providing transaction management;

a database engine connecting the concurrency controller with storage, the storage connected with the database engine comprising a first storage including a buffer pool and a second storage including second replicated data and configuration data;

a query processor connected with the database engine and configured to perform query processing;

at least one network binding component connected with the database engine.

15. The method of claim 1, wherein the concurrency control includes a recovery manager, transaction log manager, lock manager, replication engine and transaction manager.

16. The method of claim 1, wherein the database engine includes a storage manager, buffer manager, file manager, disk space manager, access control manager, and indexes and records manager.

17. The method of claim 1, wherein the replicated data of the second storage includes a transaction log and RDF repositories including a system catalog.

18. The method of claim 1, wherein the system catalog includes metadata associated with at least one slave database management server node, wherein the metadata includes database statistics, DDL functions, DDL views, DDL procedures, access control lists, disk pages, indexes, records, logical files an physical files associated with all RDF repositories of slave database nodes.

21. The method of claim 1, wherein the concurrency control includes replication engine replicating data across a plurality of slave nodes.

29. The method of claim 1, wherein the query processor receives a query or data manipulation language (DML) request and includes a query lexer, an operator evaluator, query optimizer, a plan generator, a plan cost estimator,

wherein

the query lexer parses the query or DML request into a set of tokens,

the operator evaluator generates logical operators based on the tokens,

the query optimizer optimizes the query based on the logical operators,

a plan generator generates a plurality of query plans based on the optimized query,

a plan cost estimator estimating a fastest query plan,

the query processor executes the fastest query plan.

34. The method of claim 1, wherein the buffer manager manages the buffer pool including cached disk pages on the master database server node, wherein a display page read from the second storage is cached in the buffer pool until overwritten.

35. The method of claim 1, further comprising:

a memory manager managing heap memory allocation/de-allocation using a heap memory buffer in thread local storage of the first storage.

42. The method of claim 1 further comprising:

receiving a query plan including a set of physical object operators;

executing the query plan sequentially on each of the physical object operators;

determining logical database files corresponding to the executed physical object operator;

providing concurrency control on the determined logical database files;

mapping the logical database files to physical files;

determining a node(s) the physical files are located;

retrieving the physical files from the determined node(s).

54. The method of claim 1 further comprising:

performing processing involving parsing and/or handling algebraic operators associated with the query;

performing query optimization processing including generating one or more query execution plans and estimating costs for the query execution plans;

processing a list of query evaluation plans;

evaluating, via a query plan evaluator, at least one of the query evaluation plans to select a query evaluation plan that yields a best way to physically interact with a database storage engine of the distributed database management system; and

executing the selected query execution plan.

2. A method for performing database management utilizing distributed Resource Description Framework (RDF) repositories, the method comprising:

providing transaction management via a concurrency controller;

processing data between the concurrency controller and storage via a database engine, the storage comprising a first storage including a buffer pool and a second storage including second replicated data and configuration data; and

performing query processing via a query processor connected with the database engine;

connecting at least one network binding component with the database engine, wherein the at least one network binding component comprises one or more subcomponents including a web server engine for data interchange, wherein the web server engine runs in-process with a master database node.

12. The method of claim 2, the master database node comprising:

a concurrency controller providing transaction management;

a database engine connecting the concurrency controller with storage, the storage connected with the database engine comprising a first storage including a buffer pool and a second storage including second replicated data and configuration data;

a query processor connected with the database engine and configured to perform query processing;

at least one network binding component connected with the database engine and comprising one or more subcomponents including a web server engine for data interchange, wherein the web server engine runs in-process with the master database node.

24. The method of claim 2, wherein the master server node receives federated queries via an HTTP endpoint.

3. (canceled)

5-10. -10. (canceled)

13-14. -14. (canceled)

19-20. -20. (canceled)

22-23. -23. (canceled)

25-28. -28. (canceled)

30-33. -33. (canceled)

36-38. -38. (canceled)

40-41. -41. (canceled)

43-53. -53. (canceled)

55-58. -58. (canceled)

59. A method for processing information associated with a distributed RDF database management system using ODBC, the method comprising:

connecting a master database server node to one or more slave database server nodes via a distributed database server transaction protocol (DDSTP) endpoint;

enforcing, via a distributed database server, data integrity constraints and access controls to different classes of users;

performing processing, via the distributed database server, to support atomicity, consistency, isolation and durability (ACID);

providing, via the master database server node, crash recovery by utilizing a write-ahead log (WAL);

performing processing, via the slave database server node, regarding accepting, creating, reading, updating and deleting requests (CRUD); and

serializing the distributed database management system, via snapshot isolation, involving multiversion concurrency control (SI MVCC).

39. The method of claim 59, wherein the replication engine manages database node replication and transmits DDSTP commands to slave database nodes.

73. The method of claim 59 including distributed query pre-processing, wherein some of the query processing is configured to occur in the ODBC driver, taking the processing load off the master database node.

87. The method of claim 59 wherein the DDSTP endpoint is configured to stop queries that take too long to process before the query is executed, thus preventing long running queries from consuming large amounts of database server system resources and also preventing denial of service attacks.

60-72. -72. (canceled)

74-86. -86. (canceled)