Efficient in-memory db query processing over any semi-structured data formats
US-2017060973-A1 · Mar 2, 2017 · US
US2018225314A1 · US · A1
| Field | Value |
|---|---|
| Publication number | US-2018225314-A1 |
| Application number | US-201715426988-A |
| Country | US |
| Kind code | A1 |
| Filing date | Feb 7, 2017 |
| Priority date | Feb 7, 2017 |
| Publication date | Aug 9, 2018 |
| Grant date | — |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Disclosed aspects relate to managing a single database management system (DBMS) which interfaces with both a first and second application program. A first data set corresponding to a first data format may be received by a DBMS interface engine. A second data set corresponding to a second data format may be received by the DBMS interface engine. A holistic data model to represent the first data set and the second data set may be determined by analyzing the first data set and the second data set using the DBMS interface engine. The holistic data model may be structured by the DBMS interface engine with respect to a single database of the single DBMS.
Opening claim text (preview).
What is claimed is: 1 . A computer-implemented method for managing a single database management system (DBMS) which interfaces with both a first application program that indicates a first data format and a second application program that indicates a second data format, the method comprising: receiving, by a DBMS interface engine from the first application program, a first data set corresponding to the first data format; receiving, by the DBMS interface engine from the second application program, a second data set corresponding to the second data format, wherein the first data format differs from the second data format; determining, by analyzing the first data set and the second data set using the DBMS interface engine, a holistic data model to represent the first data set and the second data set, wherein the holistic data model includes a first data construct based on the first data set and a second data construct based on the second data set; and structuring, by the DBMS interface engine, the holistic data model with respect to a single database of the single DBMS. 2 . The method of claim 1 , further comprising: receiving, by the DBMS interface engine, a first query from the first application program that indicates the first data format; receiving, by the DBMS interface engine, a second query from the second application program that indicates the second data format, wherein the first data format differs from the second data format; searching, based on the first query from the first application program that indicates the first data format, the holistic data model with respect to the single database system; searching, based on the second query from the second application program that indicates the second data format, the holistic data model with respect to the single database system; resolving, both based on and in response to searching the single database of the single DBMS, a first valid search result for the first query; resolving, both based on and in response to searching the single database of the single DBMS, a second valid search result for the second query; providing, by the DBMS interface engine, the first valid search result responsive to the first query from the first application program that indicates the first data format, wherein the first valid search result for the first query corresponds to the first data format; and providing, by the DBMS interface engine, the second valid search result responsive to the second query from the second application program that indicates the second data format, wherein the second valid search result for the second query corresponds to the second data format. 3 . The method of claim 1 , further comprising: extracting, with respect to the first data set corresponding to the first data format, a format-specific data attribute; performing, based on the format-specific data attribute with respect to the first data set; a data management action to configure the first data set for use in the holistic data model with respect to the single database management system. 4 . The method of claim 2 , further comprising: identifying, by the DBMS interface engine, that the first data format is a JavaScript Object Notation (JSON) format; identifying, by the DBMS interface engine, that the second data format is a relational format; providing, by the DBMS interface engine, the first valid search result using the JSON format; and providing, by the DBMS interface engine, the second valid search result using the relational format. 5 . The method of claim 2 , further comprising: identifying, by the DBMS interface engine, that the first data format is a relational format; identifying, by the DBMS interface engine, that the second data format is a graph format; providing, by the DBMS interface engine, the first valid search result using the relational format; and providing, by the DBMS interface engine, the second valid search result using the graph format. 6 . The method of claim 2 , further comprising: identifying, by the DBMS interface engine, that the first data format is a graph format; identifying, by the DBMS interface engine, that the second data format is a JSON format; providing, by the DBMS interface engine, the first valid search result using the graph format; and providing, by the DBMS interface engine, the second valid search result using the JSON format. 7 . The method of claim 1 , further comprising: selecting, by the DBMS interface engine, a JSON mode based on at least one data format having a JSON format; searching, using the JSON mode, the single database of the single DBMS; and resolving, using the JSON mode, at least one valid JSON search result. 8 . The method of claim 1 , further comprising: selecting, by the DBMS interface engine, a relational mode based on at least one data format having a relational format; searching, using the relational mode, the single database of the single DBMS; and resolving, using the relational mode, at least one valid relational search result. 9 . The method of claim 1 , further comprising: selecting, by the DBMS interface engine, a graph mode based on at least one data format having a graph format; searching, using the graph mode, the single database of the single DBMS; and resolving, using the graph mode, at least one valid graph search result. 10 . The method of claim 1 , further comprising: detecting that both the first query from the first application program that indicates the first data format and the second query from the second application program that indicates the second data format are from a same application program, wherein the same application program includes both the first application program and the second application program. 11 . The method of claim 1 , further comprising: modeling, using a graph having a set of vertices and a set of edges, the holistic data model with respect to the single database of the single DBMS. 12 . The method of claim 11 , further comprising: compiling, in the DBMS with respect to a key-value format, a set of spaces which includes information related to a set of typologies; constructing, in the DBMS with respect to the key-value format, a set of edges based on a set of key values of the key-value format; and identifying, in the DBMS with respect to the key-value format, a set of keys which indicates a set of values. 13 . The method of claim 11 , further comprising: compiling, in the DBMS with respect to a JSON format, a set of spaces which includes information related to a set of typologies; identifying, in the DBMS with respect to the JSON format, a primary key; structuring, in the DBMS with respect to the JSON format, a set of separate nodes to include a set of sub-documents; and structuring, in the DBMS with respect to the JSON format, an array having a set of separate data which includes a set of values which has a key that uses an array index. 14 . The method of claim 11 , further comprising: compiling, in the DBMS with respect to a relational format, a set of spaces which includes information related to a set of typologies; and constructing, in the DBMS with respect to the relational format, a set of edges based on a relationship between a plurality of respective spaces of the set of spaces. 15 . The method of claim 11 , further comprising: compiling, in the DBMS with respect to a relational format, a set of spaces which includes a respective node for a respective atomic value; and constructing, in the DBMS with respect to the relational format, a set of edges based on a relationship be
with details for data modelling support · CPC title
Query execution · CPC title
Physics · mapped topic
Physics · mapped topic
Physics · mapped topic
Related publications grouped by family.
Answers are generated from the same data shown on this page.