CN105938479B - A kind of structure conversion method of relation table and non-relation table - Google Patents
A kind of structure conversion method of relation table and non-relation table Download PDFInfo
- Publication number
- CN105938479B CN105938479B CN201610200564.9A CN201610200564A CN105938479B CN 105938479 B CN105938479 B CN 105938479B CN 201610200564 A CN201610200564 A CN 201610200564A CN 105938479 B CN105938479 B CN 105938479B
- Authority
- CN
- China
- Prior art keywords
- relation table
- hbase
- relation
- relationship
- many
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/25—Integrating or interfacing systems involving database management systems
- G06F16/258—Data format conversion from or to a database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
Landscapes
- Engineering & Computer Science (AREA)
- Databases & Information Systems (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The present invention relates to the structure conversion methods of relation table and non-relation table, the type including judging individual relation table in relevant database；If certain table is independence table, converted using simple entity transformation model；Judge the relationship between two relation tables in relevant database；One-one relationship if it exists is then converted using one-one relationship transformation model；Many-one relationship if it exists is then converted using many-one relationship transformation model；Many-to-many relationship if it exists is then converted using many-to-many relationship transformation model.The method that embodiment of the present invention provides can be converted using different transformation models for different table relationships according to the type of table in former relevant database and table relationship, be effectively retained all data relationships of original structured database.
Description
Technical field
The present invention relates to database migration field, especially a kind of structure conversion method from relation table and non-relation table.
Background technique
Big data analysis be big data application Main way, traditional Relational DBMS (RDBMS) by
Poor in scalability, the problems such as IO pressure is big under big data, and data analysis efficiency is low, has been difficult to adapt to Mass Data Management
Demand.
As HBase database is successfully used to building real-time system by Facebook, have become most popular at present
NOSQL database, not only possess the advantages of most of NOSQL database is possessed, and provide it is more powerful can
Scalability and data manipulation performance.Currently, by HBase be applied to operation system do big data analysis and data mining at
For a hot spot of big data application, Most current operation system uses relevant database storing data, in order to facilitate data
Processing, it usually needs data are migrated into HBase from relevant database.
But how RDBMS data are imported into HBase, huge challenge is still suffered from present:
The first, HBase is different from the logical construction of RDBMS: HBase is the semi-structured number sparse by one kind of column storage
According to library system, it and traditional relevant database have very big difference.The two must be taken into consideration in Data Migration to HBase
Difference, and solve this problem；
The second, data retain certain relationship in HBase: if carrying out Data Migration, number according to the scene of data analysis
A large amount of multi-condition inquiry operation certainly will be had according to, the attended operation efficiency in HBase between multilist is very low, how at one
The multirelation for retaining data in HBase table is the key that promote HBase High Performance Data Query.
Third, Data Migration performance problem: needing the reorganization of data pick-up and data during migration, these
Process is all operated along with join, and join operation is quite time-consuming, and the efficiency for how improving data join operation is to solve data
The key of migration performance.
4th, the problem of HBase table structure designs: HBase has the shortcomings that a lot compared with RDBMS, such as does not support rope
Draw, without SQL, does not support join operation etc., so a step crucial in Data Migration is exactly to design HBase table structure, it is good
Table structure can greatly improve the search efficiency of data.
Summary of the invention
It is an object of the invention to the structure conversion methods of a kind of relation table and non-relation table, can be effectively retained original knot
All data relationships of structure database, greatly improve the search efficiency of data.
For this purpose, the embodiment of the invention provides in a kind of Data Migration applied to RDBMS database to HBase database
Relation table and non-relation table structure conversion method, comprising: judge the type of individual relation table in relevant database；
If certain table is independence table, is converted, obtained in HBase database using simple entity transformation model
The non-relation table of HBase；
Judge the relationship between two relation tables in relevant database；
If two relation tables in relevant database there are one-one relationship, using one-one relationship transformation model into
Row conversion, obtains the non-relation table of HBase in HBase database；
If two relation tables in relevant database there are many-one relationship, using many-one relationship transformation model into
Row conversion, obtains the non-relation table of HBase in HBase database；
If two relation tables in relevant database there are many-to-many relationship, using many-to-many relationship transformation model into
Row conversion, obtains the non-relation table of HBase in HBase database；
Judge three in relevant database or the mutual relationship of three relation above tables；
If three or three relation above tables have one-to-many relationship between each other, complex relationship transformation model is used
It is converted, obtains the non-relation table of HBase in HBase database.
As a kind of specific embodiment, the independence table are as follows: certain relation table in relevant database does not have
Use the major key of other tables as external key, other tables are also without using the major key of the table as external key.
As a kind of specific embodiment, a pair of relationship an are as follows: table is relevant with another table, and two tables
Relationship between tuple is to correspond.
As a kind of specific embodiment, the pair of more relationships are as follows: the wherein table in two tables is closed by external key
System's two tables of connection, and the same tuple using multiple tuples of the table of external key corresponding to an other table.
As a kind of specific embodiment, the many-to-many relationship are as follows: two tables establish connection by a middle table,
And multiple tuples that two tables all at least have tuple and an other table are established and are contacted.
It is described to be converted using simple entity transformation model as a kind of specific embodiment specifically:
To each of independence Table A major keyIt willCombination, as
The row of the non-relation table of HBase is strong
To each tuple of independence Table AOne key-value pair includes each tupleEach of fieldWherein each fieldIt is the non-primary key attribute of independence Table A；
One column family cf of the non-relation table of HBaseAIn column by the non-primary key set f in independence Table AAComposition.
It is described to be converted specially using one-one relationship transformation model as a kind of specific embodiment are as follows:
Defining the first relation table A and the second relation table B is one-one relationship, and the external key of the first relation table A is the second relationship
The major key of table B, third relation table C is merge table of the first relation table A with the second relation table B by outer connection, and first closes
The major key for being Table A is the major key of third relation table C；
First relation table A is merged into third relation table C by outer connection generation with the second relation table B；
Third relation table C is converted using simple entity transformation model, generates the corresponding non-relation table of HBase.
It is described to be converted using many-one relationship transformation model as a kind of specific embodiment specifically:
Defining the first relation table A and the second relation table B is many-one relationship, and the external key of the second relation table B is the first relationship
The major key of Table A, and the external key of multiple tuples is the major key of the first same tuple of relation table A in the second relation table B；First HBase
Non- relation table HA is non-relation table corresponding with the first relation table A in HBase database, and the 2nd HBase is non-, and relation table HB is
Non- relation table corresponding with the second relation table B in HBase database；
Be one-one relationship with the first relation table A for the second relation table B, using one-one relationship transformation model into
Row is converted to the non-relation table HB of the 2nd HBase；
It for the first relation table A, is first converted using simple entity, is converted into the corresponding non-relation table HA of first HBase,
It is each non-master key field of the second relation table B in the non-relation table HA of first HBaseCreate column familyBased on one-to-many
Relationship, a tuple in the first relation table AMajor keyThere is a tupleAnd It isExternal key；
In tupleIn, the row of a key-value pair is strong to beIt is column familyColumn limit
Symbol, the non-master key field of the second relation table BIt is the value of this column.
It is described to be converted using many-to-many relationship transformation model as a kind of specific embodiment specifically:
Define the first relation table A and the second relation table B be many-one relationship, third relation table C be by the first relation table A with
Second relation table B generate intermediate interactions table, the non-relation table HA of the first HBase be HBase database in A pairs of the first relation table
The non-relation table answered, the non-relation table HB of the 2nd HBase are non-relation table corresponding with the second relation table B in HBase database；
For the first relation table A, since the first relation table A and the second relation table B are many-one relationships, first using one-to-many
Relationship transformation model is converted to the first table of the non-relation table HA of the first HBase, then due to the first relation table A and third relation table
C is also many-one relationship, and the first table of relation table HA non-to the first HBase uses many-one relationship transformation model to be converted to again
The non-relation table HA of one HBase；
For the second relation table B, since the second relation table B and the first relation table A are many-one relationships, first using one-to-many
Relationship transformation model is converted to the first table of the non-relation table HB of the 2nd HBase, then due to the second relation table B and third relation table
C is also many-one relationship, and the first table of relation table B non-to the 2nd HBase uses many-one relationship transformation model to be converted to again
The non-relation table HB of two HBase.
Compared with prior art, the structure conversion method of embodiment of the present invention provides relation table and non-relation table can be with
It, can be according to table in former relevant database when converting table structure to the Data Migration of HBase database from RDBMS database
Type and table relationship, converted for different table relationships using different transformation models, be effectively retained original structure
Change all data relationships of database.
Detailed description of the invention
Fig. 1 is the flow chart of one embodiment of method of the invention；
Fig. 2 is the building-block of logic of simple entity transformation model described in the embodiment of the present invention；
Fig. 3 is the building-block of logic of the one-to-one transformation model of the embodiment of the present invention；
Fig. 4 is the building-block of logic of the one-to-many transformation model of the embodiment of the present invention；
Fig. 5 is the building-block of logic of multi-to-multi transformation model of the embodiment of the present invention.
Specific embodiment
With reference to the accompanying drawing, embodiments of the present invention are described further.In order to be fully understood from mesh of the invention
, feature and effect, make below with reference to technical effect of the attached drawing 1-5 to design of the invention, specific structure and generation into one
Walk explanation.
As shown in Figure 1, a kind of relation table in Data Migration applied to RDBMS database to HBase database with it is non-
The structure conversion method of relation table, comprising:
Step 101, the type for judging individual relation table in relevant database；If certain table is independence table,
It is converted using simple entity transformation model, obtains the non-relation table of HBase in HBase database.
As shown in Fig. 2, being the building-block of logic of simple entity transformation model in the present embodiment, in the non-relation table HA of HBase
Middle creation one column family A_INFO is managed qualifier (qualifiers), name of the attribute-name in entity table as qualifier
Word.The definition when carrying out model conversion of the name of column family.Wherein, the independence table are as follows: certain in relevant database is opened
Relation table does not use the major key of other tables as external key, other tables are also without using the major key of the table as external key.
In order to facilitate the feature of the first predefined relation table A of model conversion:
1、pkAIt is the major key of Table A, pkAIt can be made of one or more field for becoming primary key attribute.
2, assume1≤e≤k is primary key attribute set, and k is the number of the primary key attribute in Table A.
3、K < d≤q+k, q are the non-primary key attribute numbers in Table A, and pkAΙfA=φ.
4, Table A has a series of tupleComposition, each tupleThere is primary key attributeAnd non-primary key
Attribute
The transformation model of simple entity is exactly to create the corresponding HBase table HA of relation table A, and create RowKey for HAModel conversion process is divided into two steps:
The row that the first step defines HA is good for RowKey；
Second step defines the column family (column family) of HA.
By upper, the use simple entity transformation model can be obtained and converted, detailed process is as follows:
1, to each of independence Table A major keyIt willCombination, as
The row of the non-relation table HA of HBase is strong
2, to each tuple of independence Table AOne key-value pair (Key-Value Pair) includes each member
GroupEach of fieldWherein each fieldIt is the non-primary key attribute of independence Table A；
3, a column family cf of the non-relation table HA of HBaseAIn column by the non-primary key set f in independence Table AAComposition.
Step 102 judges relationship between two relation tables in relevant database, specifically includes:
If there are one-one relationships for two relation tables in step 1021, relevant database, one-one relationship is used
Transformation model is converted, and the non-relation table of HBase in HBase database is obtained.
Wherein, a pair of relationship an are as follows: table is relevant with another table, and the relationship between two list cell groups is one
One is corresponding.
Fig. 3 is the building-block of logic of one-to-one transformation model in the present invention, and the external key Bid of the first relation table A is the second pass
It is the major key of table B, two tables can actually be merged into a third relation table C (in database Connection inquiring by outer connection
Shi Jingchang is used), using the major key of a table as this opening and closing and table major key.Therefore one-to-one relational model is converted actually
It is that table C is converted into corresponding HBase table by simply physical model.
It is described to be converted using one-one relationship transformation model specifically:
1, defining the first relation table A and the second relation table B is one-one relationship, and the external key of the first relation table A is the second pass
It is the major key of table B, third relation table C is merge table of the first relation table A with the second relation table B by outer connection, and first
The major key of relation table A is the major key of third relation table C；
2, the first relation table A is merged into third relation table C by outer connection generation with the second relation table B；
3, third relation table C is converted using simple entity transformation model Entity (C), generates corresponding HBase
Non- relation table.
The non-relation table HC of HBase is obtained according to above-mentioned model conversion, as shown in Fig. 2, after connecting merging outside Table A and table B,
The attribute of table B is inserted into the corresponding row of Table A, is then collectively stored in a column family of HC.The major key of Table A is set as HC
Row it is strong.
If there are many-one relationships for two relation tables in step 1022, relevant database, many-one relationship is used
Transformation model is converted, and the non-relation table of HBase in HBase database is obtained.
Wherein, the pair of more relationships are as follows: the wherein table in two tables connects two tables by foreign key relationship, and makes
Correspond to the same tuple of an other table with multiple tuples of the table of external key.
Referring to fig. 4, Fig. 4 is the building-block of logic of one-to-many transformation model in the present embodiment.As shown in figure 4, relation table A with
Table B has one-to-many relationship, from another perspective it is considered that B and A has one-one relationship 1-1 (B, A).To 1-1 (B,
A) relationship is applicable in one-one relationship transformation model and obtains HBase table HB, the corresponding major key of storage table A and attribute in HB.From a pair
From the point of view of more, multiple corresponding relationships being recorded in table B that we must save in Table A.Restriction is used in HBase
The attribute of symbol is strong come the row for indicating B, therefore creates a column family for each attribute of B, and use the major key of B as qualifier
To store the attribute value of B.The major key of table B similar with simple entity model conversion may have multiple fields, it is therefore desirable to by the master of B
Key field synthesizes a single value.To sum up, steps are as follows for many-one relationship 1-m-single (A, B) model conversion:
1, assume: A and B has many-one relationship 1-m (A, B) in relational database, and one of Table A is recorded in table B
In have it is a plurality of record it is corresponding.
2, applicable models 1-1 (B, A) generates corresponding HTable HB, and the row that the major key of B is set as HB is good for.
3, applicable models 1-m (A, B) generates corresponding HTable HA, the data of HA storage table B.
It is specifically, described to be converted using many-one relationship transformation model specifically:
1, defining the first relation table A and the second relation table B is many-one relationship, and the external key of the second relation table B is the first pass
It is the major key of Table A, and the external key of multiple tuples is the major key of the first same tuple of relation table A in the second relation table B.First
The non-relation table HA of HBase is non-relation table corresponding with the first relation table A in HBase database, the non-relation table HB of the 2nd HBase
For non-relation table corresponding with the second relation table B in HBase database.
2, for the second relation table B, it is one-one relationship with the first relation table A, uses one-one relationship transformation model
It carries out being converted to the non-relation table HB of the 2nd HBase.
3, it for the first relation table A, is first converted using simple entity, is converted into the corresponding non-relation table HA of first HBase,
Each the non-master key field for being the second relation table B in the non-relation table HA of the first HBaseCreate column familyBased on a pair
More relationships, a tuple in the first relation table AMajor keyThere is a tupleAnd It isExternal key；In tupleIn, the row of a key-value pair is strong to beIt is column
RaceColumn qualifier, the non-master key field of the second relation table BIt is the value of this column.
If there are many-to-many relationships for two relation tables in step 1023, relevant database, many-to-many relationship is used
Transformation model is converted, and the non-relation table of HBase in HBase database is obtained.
Wherein, the many-to-many relationship are as follows: two tables establish connection by a middle table, and two tables are all at least deposited
It establishes and contacts in multiple tuples of a tuple and an other table.
It is the building-block of logic of one-to-many transformation model in the present invention referring to Fig. 5, Fig. 5.
First relation table A as shown in Figure 5 and the second relation table B has the relationship of multi-to-multi, but passes through intermediate interactions table,
Third relation table C expresses the relationship between them.So one can consider that m-n (A, B) be two 1-m relationships (1-m (A,
B) and 1-m (B, A)).In addition, C table is the relation table as caused by A and B, A, B and C table have many-one relationship.Therefore more
Need to do two many-one relationship model conversions for being just in many-many relationship transformation model.Exist because table C relies on A, B,
C table information is not saved individually.The non-relation table HA of first HBase (HBase HA) creates the data of BE, BF column family storage table B, the
The data of non-relation table HB creation AD, AE column family storage A table of two HBase, are then respectively created column family CE storage C table in HA, HB
Data.So the conversion process of many-to-many relationship transformation model can split into four many-one relationship models.To sum up, converted
Journey is as follows:
1, assume: entity A entity B has many-one relationship to assume that an entity, table C are the intermediate interactions generated by A and B
Table.
2,1-m (A, B) first is carried out, then 1-m (A, C) obtains HA.
3,1-m (B, A) first is carried out, then 1-m (B, C) obtains HB.
It is specifically, described to be converted using many-to-many relationship transformation model are as follows:
Define the first relation table A and the second relation table B be many-one relationship, third relation table C be by the first relation table A with
Second relation table B generate intermediate interactions table, the non-relation table HA of the first HBase be HBase database in A pairs of the first relation table
The non-relation table answered, the non-relation table HB of the 2nd HBase are non-relation table corresponding with the second relation table B in HBase database.
For the first relation table A, since the first relation table A and the second relation table B are many-one relationships, first using one-to-many
Relationship transformation model is converted to the first table of the non-relation table HA of the first HBase, then due to the first relation table A and third relation table
C is also many-one relationship, and the first table of relation table HA non-to the first HBase uses many-one relationship transformation model to be converted to again
The non-relation table HA of one HBase.
For the second relation table B, since the second relation table B and the first relation table A are many-one relationships, first using one-to-many
Relationship transformation model is converted to the first table of the non-relation table HB of the 2nd HBase, then due to the second relation table B and third relation table
C is also many-one relationship, and the first table of relation table B non-to the 2nd HBase uses many-one relationship transformation model to be converted to again
The non-relation table HB of two HBase.
The structure conversion method of relation table and non-relation table that embodiment of the present invention provides can be from RDBMS database
To HBase database Data Migration convert table structure when, can according to the type of table in former relevant database and table relationship,
It is converted for different table relationships using different transformation models, has been effectively retained all numbers of original structured database
According to relationship.
It should be understood that the invention is not limited to above embodiment, it is all to various changes or modifications of the invention not
Be detached from the spirit and scope of the present invention, if these modification and variations belong to claim and equivalent technologies range of the invention it
Interior, then the present invention is also implied that comprising these modification and variations.
Claims (7)
1. the structure conversion method of a kind of relation table and non-relation table, the number applied to RDBMS database to HBase database
According in migration characterized by comprising
Judge the type of individual relation table in relevant database；
If certain table is independence table, is converted, obtained in HBase database using simple entity transformation model
The non-relation table of HBase；It is described to be converted using simple entity transformation model specifically:
To each of independence Table A major keyIt willCombination, it is non-as HBase
The row of relation table is strong
To each tuple of independence Table AOne key-value pair includes each tupleEach of field
Wherein each fieldIt is the non-primary key attribute of independence Table A；
One column family cf of the non-relation table of HBaseAIn column by the non-primary key set f in independence Table AAComposition；
Judge the relationship between two relation tables in relevant database；
If there are one-one relationships for two relation tables in relevant database, turned using one-one relationship transformation model
It changes, obtains the non-relation table of HBase in HBase database；
If there are many-one relationships for two relation tables in relevant database, turned using many-one relationship transformation model
It changes, obtains the non-relation table of HBase in HBase database；
Defining the first relation table A and the second relation table B is many-one relationship, and the external key of the second relation table B is the first relation table A
Major key, and the external key of multiple tuples is the major key of the first same tuple of relation table A in the second relation table B；The first non-relationship of HBase
Table HA is non-relation table corresponding with the first relation table A in HBase database, and the non-relation table HB of the 2nd HBase is HBase data
Non- relation table corresponding with the second relation table B in library；
For the second relation table B, it is one-one relationship with the first relation table A, is turned using one-one relationship transformation model
It gets in return to the non-relation table HB of the 2nd HBase；
It for the first relation table A, is first converted using simple entity, the corresponding non-relation table HA of first HBase is converted into, first
It is each non-master key field of the second relation table B in the non-relation table HA of HBaseCreate column familyBased on one-to-many pass
It is a tuple in the first relation table AMajor keyThere is a tupleAnd It isExternal key；
In tupleIn, the row of a key-value pair is strong to be It is column familyColumn qualifier,
The non-master key field of two relation table BIt is the value of this column；
If there are many-to-many relationships for two relation tables in relevant database, turned using many-to-many relationship transformation model
It changes, obtains the non-relation table of HBase in HBase database.
2. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that the independence
Table are as follows: certain relation table in relevant database does not use the major key of other tables as external key, other tables also do not use
The major key of the table is as external key.
3. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that the pair of one closes
System an are as follows: table is relevant with another table, and the relationship between two list cell groups is to correspond.
4. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that the pair of more passes
System are as follows: the wherein table in two tables connects two tables by foreign key relationship, and corresponding using multiple tuples of the table of external key
In the same tuple of an other table.
5. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that the multi-to-multi closes
System are as follows: two tables establish connection by a middle table, and two tables all at least have a tuple and an other table
Multiple tuples establish connection.
6. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that described using a pair of
One relationship transformation model is converted specifically:
Defining the first relation table A and the second relation table B is one-one relationship, and the external key of the first relation table A is the second relation table B
Major key, third relation table C are merge table of the first relation table A with the second relation table B by outer connection, and the first relation table A
Major key be third relation table C major key；
First relation table A is merged into third relation table C by outer connection generation with the second relation table B；
Third relation table C is converted using simple entity transformation model, generates the corresponding non-relation table of HBase.
7. the structure conversion method of relation table as described in claim 1 and non-relation table, which is characterized in that described using multipair
More relationship transformation models are converted specifically:
Defining the first relation table A and the second relation table B is many-one relationship, and third relation table C is by the first relation table A and second
The intermediate interactions table that relation table B is generated, the non-relation table HA of the first HBase are corresponding with the first relation table A in HBase database
Non- relation table, the non-relation table HB of the 2nd HBase are non-relation table corresponding with the second relation table B in HBase database；
For the first relation table A, since the first relation table A and the second relation table B are many-one relationships, many-one relationship is first used
Transformation model is converted to the first table of the non-relation table HA of the first HBase, then due to the first relation table A and third relation table C
It is many-one relationship, the first table of relation table HA non-to the first HBase uses many-one relationship transformation model to be converted to first again
The non-relation table HA of HBase；
For the second relation table B, since the second relation table B and the first relation table A are many-one relationships, many-one relationship is first used
Transformation model is converted to the first table of the non-relation table HB of the 2nd HBase, then due to the second relation table B and third relation table C
It is many-one relationship, the first table of relation table B non-to the 2nd HBase uses many-one relationship transformation model to be converted to second again
The non-relation table HB of HBase.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610200564.9A CN105938479B (en) | 2016-03-31 | 2016-03-31 | A kind of structure conversion method of relation table and non-relation table |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610200564.9A CN105938479B (en) | 2016-03-31 | 2016-03-31 | A kind of structure conversion method of relation table and non-relation table |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN105938479A CN105938479A (en) | 2016-09-14 |
| CN105938479B true CN105938479B (en) | 2019-10-22 |
Family
ID=57151987
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610200564.9A Active CN105938479B (en) | 2016-03-31 | 2016-03-31 | A kind of structure conversion method of relation table and non-relation table |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN105938479B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| TW201820175A (en) * | 2016-11-22 | 2018-06-01 | 財團法人資訊工業策進會 | Data base transformation server and data base transformation method thereof |
| CN106682173B (en) * | 2016-12-28 | 2019-10-18 | 华南理工大学 | A kind of social security big data OLAP preprocess method and on-line analysis querying method |
| CN108920519A (en) * | 2018-06-04 | 2018-11-30 | 贵州数据宝网络科技有限公司 | One-to-many data supply system and method |
| CN110032604B (en) * | 2019-02-02 | 2021-12-07 | 北京奥星贝斯科技有限公司 | Data storage device, translation device and database access method |
| CN110262969B (en) * | 2019-06-13 | 2022-03-22 | 泰康保险集团股份有限公司 | Report testing method and device, electronic equipment and computer readable storage medium |
| CN110688433B (en) * | 2019-12-10 | 2020-04-21 | 银联数据服务有限公司 | Path-based feature generation method and device |
| CN113901031A (en) * | 2021-10-21 | 2022-01-07 | 掌阅科技股份有限公司 | Database migration method, electronic device and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102308297A (en) * | 2011-07-13 | 2012-01-04 | 华为技术有限公司 | Data migration method, data migration device and data migration system |
| CN103530327A (en) * | 2013-09-25 | 2014-01-22 | 清华大学深圳研究生院 | Method for migrating data from non-relational database to relational database |
| WO2014088396A2 (en) * | 2012-12-05 | 2014-06-12 | Mimos Berhad | Automatic transformation of non-relational database into relational database |
| CN104123392A (en) * | 2014-08-11 | 2014-10-29 | 吉林禹硕动漫游戏科技股份有限公司 | Tool and method for transferring relational database to HBase |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9529875B2 (en) * | 2014-01-13 | 2016-12-27 | International Business Machines Corporation | Transforming timeseries and non-relational data to relational for complex and analytical query processing |
-
2016
- 2016-03-31 CN CN201610200564.9A patent/CN105938479B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102308297A (en) * | 2011-07-13 | 2012-01-04 | 华为技术有限公司 | Data migration method, data migration device and data migration system |
| WO2014088396A2 (en) * | 2012-12-05 | 2014-06-12 | Mimos Berhad | Automatic transformation of non-relational database into relational database |
| CN103530327A (en) * | 2013-09-25 | 2014-01-22 | 清华大学深圳研究生院 | Method for migrating data from non-relational database to relational database |
| CN104123392A (en) * | 2014-08-11 | 2014-10-29 | 吉林禹硕动漫游戏科技股份有限公司 | Tool and method for transferring relational database to HBase |
Also Published As
| Publication number | Publication date |
|---|---|
| CN105938479A (en) | 2016-09-14 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN105938479B (en) | A kind of structure conversion method of relation table and non-relation table | |
| Zhao et al. | Modeling MongoDB with relational model | |
| CN109669934B (en) | Data warehouse system suitable for electric power customer service and construction method thereof | |
| CN106227800B (en) | Storage method and management system for highly-associated big data | |
| CN104504008B (en) | A kind of Data Migration algorithm based on nested SQL to HBase | |
| CN102346775A (en) | Method for synchronizing multiple heterogeneous source databases based on log | |
| US10002142B2 (en) | Method and apparatus for generating schema of non-relational database | |
| CN110222029A (en) | A kind of big data multidimensional analysis computational efficiency method for improving and system | |
| CN103810219B (en) | Line storage database-based data processing method and device | |
| Giannakouris et al. | MuSQLE: Distributed SQL query execution over multiple engine environments | |
| CN102270232A (en) | Semantic data query system with optimized storage | |
| CN107506464A (en) | A kind of method that HBase secondary indexs are realized based on ES | |
| CN103678550A (en) | Mass data real-time query method based on dynamic index structure | |
| Goyal et al. | Cross platform (RDBMS to NoSQL) database validation tool using bloom filter | |
| CN105022791A (en) | Novel KV distributed data storage method | |
| CN110597876B (en) | Approximate query method for predicting future query based on offline learning historical query | |
| CN104268158A (en) | Structural data distributed index and retrieval method | |
| CN109165262A (en) | Fragmentation clustering system and fragmentation method of relational large table | |
| CN108319604B (en) | Optimization method for association of large and small tables in hive | |
| CN107506394B (en) | Optimization method for eliminating big data standard relation connection redundancy | |
| CN109686413A (en) | A kind of chemical molecular formula search method based on es inverted index | |
| CN103186674A (en) | Web data quick inquiry method based on extensive makeup language (XML) | |
| CN103279580A (en) | Video retrieval method based on novel semantic space | |
| CN114791935A (en) | Method for realizing high-performance multidimensional data warehouse based on cloud object storage | |
| CN103617181A (en) | Method and device for establishing universal database of relationships |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20230802 Address after: Building G1, No. 17, Software Road, Tianhe District, Guangzhou, Guangdong 510660 Patentee after: GUANGZHOU BINGO SOFTWARE CO.,LTD. Address before: 510631 School of computer science, South China Normal University, 55 West Zhongshan Road, Guangzhou, Guangdong Patentee before: SOUTH CHINA NORMAL University |