CN111897793A - Data importing method and device, electronic equipment and computer-readable storage medium - Google Patents
Data importing method and device, electronic equipment and computer-readable storage medium Download PDFInfo
- Publication number
- CN111897793A CN111897793A CN202010569855.1A CN202010569855A CN111897793A CN 111897793 A CN111897793 A CN 111897793A CN 202010569855 A CN202010569855 A CN 202010569855A CN 111897793 A CN111897793 A CN 111897793A
- Authority
- CN
- China
- Prior art keywords
- data
- migrated
- database
- neo4j
- importing
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 39
- 230000005012 migration Effects 0.000 claims description 44
- 238000013508 migration Methods 0.000 claims description 44
- 230000008676 import Effects 0.000 claims description 19
- 230000002159 abnormal effect Effects 0.000 claims description 7
- 238000006243 chemical reaction Methods 0.000 claims description 6
- 238000004590 computer program Methods 0.000 claims description 6
- 230000006870 function Effects 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000005034 decoration Methods 0.000 description 2
- 238000002955 isolation Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000011022 operating instruction Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000013499 data model Methods 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 235000019800 disodium phosphate Nutrition 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000002093 peripheral effect Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
Images
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/21—Design, administration or maintenance of databases
- G06F16/214—Database migration support
-
- 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/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9024—Graphs; Linked lists
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)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the application provides a data importing method and device, electronic equipment and a computer readable storage medium. The method comprises the following steps: acquiring a conceptual model of a relational database, and acquiring a data table to be migrated based on the conceptual model; converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated; a Neo4j database is created based on the data files. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
Description
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a data importing method and apparatus, an electronic device, and a computer-readable storage medium.
Background
In the relational database, the relationship between data is realized by the row-column relationship between tables, the query efficiency is low, and particularly, when the number of data records is too large, the query performance is low even if the query is simple.
The graphic database Neo4j adopts a graph processing structure with a free adjacency characteristic, can provide a flexible data model with fast transaction processing and data relation processing performance, can add data types at will, can modify and change data and data types at any time and any place without depending on data quantity and data depth, does not weaken the performance along with the increase of the data quantity and the increase of the depth, provides a Cypher graph query language, provides the most effective expression mode for describing relations, supports Atomicity (Atomicity), Consistency (Consistency), Isolation (Isolation) and Durability (durabilty), and ensures data Consistency and reliability.
With the increasing amount of data in financial systems and the increasing complexity of relational query logic, the conventional relational database cannot meet the use requirement, and data needs to be migrated to the database Neo4j to support more efficient data storage and data query.
At present, data is generally imported into Neo4j by directly using an Extract-Transform-Load (ETL) tool, which is inefficient in data import, prone to errors during import, and not easy to operate.
Disclosure of Invention
The present application aims to solve at least one of the above technical drawbacks. The technical scheme adopted by the application is as follows:
in a first aspect, an embodiment of the present application provides a data importing method, where the method includes:
acquiring a conceptual model of a relational database, and acquiring a data table to be migrated based on the conceptual model;
converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
a Neo4j database is created based on the data files.
Optionally, converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated, including:
and respectively converting the first migration table without the external key in the table to be migrated and the second migration table with the external key in the table to be migrated into corresponding CSV files.
Optionally, creating a Neo4j database based on the data files, including:
creating a Neo4j database;
importing the CSV file corresponding to the first migration table into a Neo4j database through a Neo4j load tool;
and importing the CSV file corresponding to the second migration table into a Neo4j database through a Neo4j import tool.
Optionally, the method further includes:
when target data is imported into a Neo4j database, determining a target migration data table of the target data;
and converting the target migration data table into a CSV file, and importing the CSV file into a Neo4j database through a Neo4j load tool.
Optionally, the method further includes:
and importing abnormal data which do not meet preset conditions in the relational database into the Neo4j database through a Cypyher CREATE statement.
Optionally, the method further includes:
data that does not belong to the external of the relational database is imported into the Neo4j database through the Cypyher CREATE statement.
In a second aspect, an embodiment of the present application provides an apparatus for importing data, where the apparatus includes:
the data table to be migrated acquiring module is used for acquiring a conceptual model of the relational database and acquiring the data table to be migrated based on the conceptual model;
the data file conversion module is used for converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
and the database creating module is used for creating a Neo4j database based on the data files.
Optionally, the data file conversion module is specifically configured to:
and respectively converting the first migration table without the external key in the table to be migrated and the second migration table with the external key in the table to be migrated into corresponding CSV files.
Optionally, the database creation module is specifically configured to:
creating a Neo4j database;
importing the CSV file corresponding to the first migration table into a Neo4j database through a Neo4j load tool;
and importing the CSV file corresponding to the second migration table into a Neo4j database through a Neo4j import tool.
Optionally, the apparatus further includes a target data import module, where the target data import module is configured to:
when target data is imported into a Neo4j database, determining a target migration data table of the target data;
and converting the target migration data table into a CSV file, and importing the CSV file into a Neo4j database through a Neo4j load tool.
Optionally, the database creating module is further configured to:
and importing abnormal data which do not meet preset conditions in the relational database into the Neo4j database through a Cypyher CREATE statement.
Optionally, the database creating module is further configured to:
data that does not belong to the external of the relational database is imported into the Neo4j database through the Cypyher CREATE statement.
In a third aspect, an embodiment of the present application provides an electronic device, including: a processor and a memory;
a memory for storing operating instructions;
a processor, configured to execute the importing method of data as shown in any implementation manner of the first aspect of the present application by calling an operation instruction.
In a fourth aspect, the present application provides a computer-readable storage medium, on which a computer program is stored, where the computer program, when executed by a processor, implements the importing method of data shown in any implementation manner of the first aspect of the present application.
The technical scheme provided by the embodiment of the application has the following beneficial effects:
according to the scheme provided by the implementation of the application, the concept model of the relational database is obtained, the data table to be migrated is obtained based on the concept model, the table to be migrated is converted into the data file in the specified format based on the relational attribute of the table to be migrated, and the Neo4j database is created based on the data file. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the description of the embodiments of the present application will be briefly described below.
Fig. 1 is a schematic flowchart of a data importing method according to an embodiment of the present disclosure;
fig. 2 is a schematic structural diagram of a data importing apparatus according to an embodiment of the present disclosure;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
Reference will now be made in detail to embodiments of the present application, examples of which are illustrated in the accompanying drawings, wherein like or similar reference numerals refer to the same or similar elements or elements having the same or similar function throughout. The embodiments described below with reference to the drawings are exemplary only for the purpose of explaining the present application and are not to be construed as limiting the present invention.
As used herein, the singular forms "a", "an", "the" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. It will be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element or intervening elements may also be present. Further, "connected" or "coupled" as used herein may include wirelessly connected or wirelessly coupled. As used herein, the term "and/or" includes all or any element and all combinations of one or more of the associated listed items.
To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.
The following describes the technical solutions of the present application and how to solve the above technical problems with specific embodiments. The following several specific embodiments may be combined with each other, and details of the same or similar concepts or processes may not be repeated in some embodiments. Embodiments of the present application will be described below with reference to the accompanying drawings.
Fig. 1 shows a schematic flowchart of a data importing method provided in an embodiment of the present application, and as shown in fig. 1, the method mainly includes:
step S110: acquiring a conceptual model of a relational database, and acquiring a data table to be migrated based on the conceptual model;
step S120: converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
step S130: a Neo4j database is created based on the data files.
In the implementation of the application, when data in the relational database is imported into a Neo4j database, a conceptual model of the relational database can be extracted, and the conceptual model mainly comprises a migration data table and a main foreign key relationship.
In the implementation of the application, the data table to be migrated can be extracted from the conceptual model, and the relationship attribute of the data table to be migrated is determined, wherein the relationship attribute can be determined based on the main foreign key relationship.
Because the data tables to be migrated with different main foreign key relationships need to be converted into corresponding data files and imported, the relationship attributes of the data tables to be migrated need to be distinguished.
In the implementation of the application, the data tables to be migrated with different relation attributes are respectively converted into the data files with the specified format, so that the Neo4j database is respectively imported into different data files when the Neo4j database is created.
According to the method provided by the implementation of the application, the conceptual model of the relational database is obtained, the data table to be migrated is obtained based on the conceptual model, the table to be migrated is converted into the data file in the specified format based on the relational attribute of the table to be migrated, and the Neo4j database is created based on the data file. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
In an optional manner of the embodiment of the present application, converting a table to be migrated into a data file in a specified format based on a relationship attribute of the table to be migrated includes:
and respectively converting a first migration table without external keys in the table to be migrated and a second migration table with external keys in the table to be migrated into corresponding Comma-Separated Values (CSV) files.
In the embodiment of the present application, the relationship attributes of the to-be-migrated table may be distinguished according to whether there is a foreign key in the to-be-migrated table, specifically, if there is no foreign key in the to-be-migrated table, the to-be-migrated table is an independent node without a relationship, and may be determined as the first migration table; if the foreign key exists in the table to be migrated, the migration table is a relationship or a node having a relationship, and may be determined as the second migration table.
And respectively converting the first migration table and the second migration table into corresponding CSV files, and directly importing the CSV files into a Neo4j database.
In an optional manner of the embodiment of the present application, creating a Neo4j database based on a data file includes:
creating a Neo4j database;
importing the CSV file corresponding to the first migration table into a Neo4j database through a Neo4j load tool;
and importing the CSV file corresponding to the second migration table into a Neo4j database through a Neo4j import tool.
In the embodiment of the present application, the number of the second migration tables is large, and the Neo4j import tool is suitable for batch import of CSV files with a large number, generally more than ten million, so that CSV files corresponding to the second migration tables can be imported into the Neo4j database through the Neo4 jimmont tool.
Compared with the neo4j import tool, the neo4j load tool is suitable for batch import of a small number of CSV files, and is generally 1 to 10 ten thousand. The number of the first migration tables is relatively small, so that the first migration tables can be imported into a Neo4j database through a Neo4j load tool.
In an optional manner of the embodiment of the present application, the method further includes:
when target data is imported into a Neo4j database, determining a target migration data table of the target data;
and converting the target migration data table into a CSV file, and importing the CSV file into a Neo4j database through a Neo4j load tool.
In the embodiment of the application, after the Neo4j database is created for the first time and initial data is imported, the data may be imported into the Neo4j database again, and since the amount of data to be imported may be relatively small and the Neo4j import tool is generally used when the Neo4j database is created, the data may be imported by the Neo4j load tool.
Specifically, the target data is data that needs to be imported into the existing Neo4j database, a target migration data table of the target data may be determined, the target migration data table is converted into a CSV file, and the CSV file is imported into the Neo4j database through a Neo4j load tool.
In an optional manner of the embodiment of the present application, the method further includes:
and importing abnormal data which do not meet preset conditions in the relational database into the Neo4j database through a Cypyher CREATE statement.
In an optional manner of the embodiment of the present application, the method further includes:
data that does not belong to the external of the relational database is imported into the Neo4j database through the Cypyher CREATE statement.
In the embodiment of the present application, some abnormal data, such as incomplete data, may exist in the relational database, and it may be considered that the abnormal data is adjusted and then imported into the Neo4j database through a Cypyher CREATE statement.
In the embodiment of the application, the situation that external data which does not belong to the relational database is imported into the Neo4j database may be encountered, and the external data can be imported into the Neo4j database through a Cypyher CREATE statement.
In actual use, when data is imported into the Neo4j database, different import strategies can be respectively determined for data tables, and all data can be imported according to the import strategies, so that the import efficiency is high, manual operation can be reduced, and the data accuracy is ensured.
Based on the same principle as the method shown in fig. 1, fig. 2 shows a schematic structural diagram of an apparatus for importing data provided by an embodiment of the present application, and as shown in fig. 2, the apparatus for importing data 20 may include:
a to-be-migrated data table obtaining module 210, configured to obtain a conceptual model of the relational database, and obtain a to-be-migrated data table based on the conceptual model;
the data file conversion module 220 is configured to convert the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
a database creation module 230 for creating a Neo4j database based on the data files.
According to the device provided by the application, the conceptual model of the relational database is obtained, the data table to be migrated is obtained based on the conceptual model, the data file in the specified format is converted from the table to be migrated based on the relational attribute of the table to be migrated, and the Neo4j database is created based on the data file. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
Optionally, the data file conversion module is specifically configured to:
and respectively converting the first migration table without the external key in the table to be migrated and the second migration table with the external key in the table to be migrated into corresponding CSV files.
Optionally, the database creation module is specifically configured to:
creating a Neo4j database;
importing the CSV file corresponding to the first migration table into a Neo4j database through a Neo4j load tool;
and importing the CSV file corresponding to the second migration table into a Neo4j database through a Neo4j import tool.
Optionally, the apparatus further includes a target data import module, where the target data import module is configured to:
when target data is imported into a Neo4j database, determining a target migration data table of the target data;
and converting the target migration data table into a CSV file, and importing the CSV file into a Neo4j database through a Neo4j load tool.
Optionally, the database creating module is further configured to:
and importing abnormal data which do not meet preset conditions in the relational database into the Neo4j database through a Cypyher CREATE statement.
Optionally, the database creating module is further configured to:
data that does not belong to the external of the relational database is imported into the Neo4j database through the Cypyher CREATE statement.
It is to be understood that the above modules of the data importing apparatus in the present embodiment have functions of implementing the corresponding steps of the data importing method in the embodiment shown in fig. 1. The function can be realized by hardware, and can also be realized by executing corresponding software by hardware. The hardware or software includes one or more modules corresponding to the functions described above. The modules can be software and/or hardware, and each module can be implemented independently or by integrating a plurality of modules. For the functional description of each module of the data importing apparatus, reference may be specifically made to the corresponding description of the data importing method in the embodiment shown in fig. 1, and details are not described here again.
The embodiment of the application provides an electronic device, which comprises a processor and a memory;
a memory for storing operating instructions;
and the processor is used for executing the data importing method provided by any embodiment of the application by calling the operation instruction.
As an example, fig. 3 shows a schematic structural diagram of an electronic device to which an embodiment of the present application is applicable, and as shown in fig. 3, the electronic device 2000 includes: a processor 2001 and a memory 2003. Wherein the processor 2001 is coupled to a memory 2003, such as via a bus 2002. Optionally, the electronic device 2000 may also include a transceiver 2004. It should be noted that the transceiver 2004 is not limited to one in practical applications, and the structure of the electronic device 2000 is not limited to the embodiment of the present application.
The processor 2001 is applied to the embodiment of the present application to implement the method shown in the above method embodiment. The transceiver 2004 may include a receiver and a transmitter, and the transceiver 2004 is applied to the embodiments of the present application to implement the functions of the electronic device of the embodiments of the present application to communicate with other devices when executed.
The Processor 2001 may be a CPU (Central Processing Unit), general Processor, DSP (Digital Signal Processor), ASIC (Application specific integrated Circuit), FPGA (Field Programmable Gate Array) or other Programmable logic device, transistor logic device, hardware component, or any combination thereof. Which may implement or perform the various illustrative logical blocks, modules, and circuits described in connection with the disclosure. The processor 2001 may also be a combination of computing functions, e.g., comprising one or more microprocessors, DSPs and microprocessors, and the like.
The Memory 2003 may be a ROM (Read Only Memory) or other type of static storage device that can store static information and instructions, a RAM (Random Access Memory) or other type of dynamic storage device that can store information and instructions, an EEPROM (Electrically erasable programmable Read Only Memory), a CD-ROM (Compact disk Read Only Memory) or other optical disk storage, optical disk storage (including Compact disk, laser disk, optical disk, digital versatile disk, blu-ray disk, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer, but is not limited to these.
Optionally, the memory 2003 is used for storing application program code for performing the disclosed aspects, and is controlled in execution by the processor 2001. The processor 2001 is configured to execute the application program code stored in the memory 2003 to implement the data importing method provided in any of the embodiments of the present application.
The electronic device provided by the embodiment of the application is applicable to any embodiment of the method, and is not described herein again.
Compared with the prior art, the electronic equipment has the advantages that the conceptual model of the relational database is obtained, the data sheet to be migrated is obtained based on the conceptual model, the data sheet to be migrated is converted into the data file in the specified format based on the relational attribute of the data sheet to be migrated, and the Neo4j database is created based on the data file. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
The embodiment of the application provides a computer-readable storage medium, and a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the computer program realizes the importing method of the data shown in the above method embodiment.
The computer-readable storage medium provided in the embodiments of the present application is applicable to any of the embodiments of the foregoing method, and is not described herein again.
Compared with the prior art, the embodiment of the application provides a computer-readable storage medium, a concept model of a relational database is obtained, a to-be-migrated data table is obtained based on the concept model, the to-be-migrated table is converted into a data file in a specified format based on the relational attributes of the to-be-migrated table, and a Neo4j database is created based on the data file. Based on the scheme, the data table to be migrated is extracted, the table to be migrated is converted into the data file with the specified format according to the relationship attribute of the table to be migrated, and then the data file is imported into the created Neo4j database, so that the table to be migrated is automatically imported into the Neo4j database, the operation is simple, the importing efficiency is high, and data errors are not prone to occurring.
It should be understood that, although the steps in the flowcharts of the figures are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and may be performed in other orders unless explicitly stated herein. Moreover, at least a portion of the steps in the flow chart of the figure may include multiple sub-steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed alternately or alternately with other steps or at least a portion of the sub-steps or stages of other steps.
The foregoing is only a partial embodiment of the present invention, and it should be noted that, for those skilled in the art, various modifications and decorations can be made without departing from the principle of the present invention, and these modifications and decorations should also be regarded as the protection scope of the present invention.
Claims (10)
1. A method for importing data, comprising:
acquiring a conceptual model of a relational database, and acquiring a data table to be migrated based on the conceptual model;
converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
a Neo4j database is created based on the data files.
2. The method according to claim 1, wherein converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated comprises:
and respectively converting the first migration table without the external key in the table to be migrated and the second migration table with the external key in the table to be migrated into corresponding comma separated value CSV files.
3. The method of claim 2, wherein creating a Neo4j database based on the data files comprises:
creating a Neo4j database;
importing the CSV file corresponding to the first migration table into the Neo4j database through a Neo4j load tool;
and importing the CSV file corresponding to the second migration table into the Neo4j database through a Neo4j import tool.
4. The method of claim 2 or 3, further comprising:
when target data is imported into the Neo4j database, determining a target migration data table of the target data;
and converting the target migration data table into a CSV file, and importing the CSV file into the Neo4j database through a Neo4jload tool.
5. The method of claim 2 or 3, further comprising:
and importing abnormal data which do not meet preset conditions in the relational database into the Neo4j database through a Cypyher CREATE statement.
6. The method of claim 2 or 3, further comprising:
data outside the relational database that does not belong to is imported into the Neo4j database via the Cypyher CREATE statement.
7. An apparatus for importing data, comprising:
a data sheet to be migrated acquiring module for acquiring the conceptual model of the relational database and acquiring the data sheet to be migrated based on the conceptual model
The data file conversion module is used for converting the table to be migrated into a data file in a specified format based on the relationship attribute of the table to be migrated;
and the database creating module is used for creating a Neo4j database based on the data files.
8. The apparatus of claim 7, wherein the data file conversion module is specifically configured to:
and respectively converting the first migration table without the external key in the table to be migrated and the second migration table with the external key in the table to be migrated into corresponding CSV files.
9. An electronic device comprising a processor and a memory;
the memory is used for storing operation instructions;
the processor is used for executing the method of any one of claims 1-7 by calling the operation instruction.
10. A computer-readable storage medium, characterized in that the storage medium has stored thereon a computer program which, when being executed by a processor, carries out the method of any one of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010569855.1A CN111897793A (en) | 2020-06-20 | 2020-06-20 | Data importing method and device, electronic equipment and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010569855.1A CN111897793A (en) | 2020-06-20 | 2020-06-20 | Data importing method and device, electronic equipment and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111897793A true CN111897793A (en) | 2020-11-06 |
Family
ID=73206365
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010569855.1A Pending CN111897793A (en) | 2020-06-20 | 2020-06-20 | Data importing method and device, electronic equipment and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111897793A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160188710A1 (en) * | 2014-12-29 | 2016-06-30 | Wipro Limited | METHOD AND SYSTEM FOR MIGRATING DATA TO NOT ONLY STRUCTURED QUERY LANGUAGE (NoSOL) DATABASE |
| CN105930361A (en) * | 2016-04-12 | 2016-09-07 | 北京恒冠网络数据处理有限公司 | Method for converting relational database into Neo4j model and data migration method |
| CN109753537A (en) * | 2019-01-25 | 2019-05-14 | 中国人民大学 | A kind of interactive data moving method from relation data to diagram data |
| CN111274495A (en) * | 2020-01-20 | 2020-06-12 | 平安科技（深圳）有限公司 | Data processing method and device for user relationship strength, computer equipment and storage medium |
-
2020
- 2020-06-20 CN CN202010569855.1A patent/CN111897793A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160188710A1 (en) * | 2014-12-29 | 2016-06-30 | Wipro Limited | METHOD AND SYSTEM FOR MIGRATING DATA TO NOT ONLY STRUCTURED QUERY LANGUAGE (NoSOL) DATABASE |
| CN105930361A (en) * | 2016-04-12 | 2016-09-07 | 北京恒冠网络数据处理有限公司 | Method for converting relational database into Neo4j model and data migration method |
| CN109753537A (en) * | 2019-01-25 | 2019-05-14 | 中国人民大学 | A kind of interactive data moving method from relation data to diagram data |
| CN111274495A (en) * | 2020-01-20 | 2020-06-12 | 平安科技（深圳）有限公司 | Data processing method and device for user relationship strength, computer equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 韩强: "一种高效的图数据抽取技术的研究", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 2015 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110704398B (en) | Database migration method and device from MySQL to Oracle and computer equipment | |
| CN102129425B (en) | The access method of big object set table and device in data warehouse | |
| CN111061758B (en) | Data storage method, device and storage medium | |
| US9600559B2 (en) | Data processing for database aggregation operation | |
| CN112861501A (en) | Report generation method and device, electronic equipment and computer readable storage medium | |
| CN111143446A (en) | Data structure conversion processing method and device of data object and electronic equipment | |
| US9971794B2 (en) | Converting data objects from multi- to single-source database environment | |
| CN112559606A (en) | Conversion method and conversion device for JSON format data | |
| CN113918605A (en) | Data query method, device, equipment and computer storage medium | |
| CN108140022B (en) | Data query method and database system | |
| CN112860802B (en) | Database operation statement processing method and device and electronic equipment | |
| CN111966707A (en) | Query statement generation method and device, electronic equipment and computer readable medium | |
| CN113407565B (en) | Cross-database data query method, device and equipment | |
| WO2021129005A1 (en) | Blockchain state change-based transaction tracking method and device | |
| CN112015831A (en) | Method, device and equipment for operating relational database based on C language | |
| CN111897793A (en) | Data importing method and device, electronic equipment and computer-readable storage medium | |
| CN113590581B (en) | Data transmission method, device, equipment and storage medium | |
| CN112488708B (en) | Block chain account relevance query method and false transaction screening method | |
| CN115617773A (en) | Data migration method, device and system | |
| CN109543079B (en) | Data query method and device, computing equipment and storage medium | |
| CN113849482A (en) | Data migration method and device and electronic equipment | |
| CN110019442B (en) | Method and device for fetching number | |
| CN112507042B (en) | Relationship map calculation method supporting incremental entity association | |
| CN112181943A (en) | Characteristic data acquisition method and device, electronic equipment and readable storage medium | |
| CN109885614B (en) | Data synchronization method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| TA01 | Transfer of patent application right | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220926 Address after: 25 Financial Street, Xicheng District, Beijing 100033 Applicant after: CHINA CONSTRUCTION BANK Corp. Address before: 25 Financial Street, Xicheng District, Beijing 100033 Applicant before: CHINA CONSTRUCTION BANK Corp. Applicant before: Jianxin Financial Science and Technology Co.,Ltd. |