CN115292277A - Data migration consistency verification method, device, system, equipment and storage medium - Google Patents

Data migration consistency verification method, device, system, equipment and storage medium Download PDF

Info

Publication number
CN115292277A
CN115292277A CN202210851510.4A CN202210851510A CN115292277A CN 115292277 A CN115292277 A CN 115292277A CN 202210851510 A CN202210851510 A CN 202210851510A CN 115292277 A CN115292277 A CN 115292277A
Authority
CN
China
Prior art keywords
migration
data
type
mapping rule
relationship
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
Application number
CN202210851510.4A
Other languages
Chinese (zh)
Inventor
许姣
汪洋
李沫
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Anhui Tingjian Technology Co ltd
Original Assignee
Anhui Tingjian Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Anhui Tingjian Technology Co ltd filed Critical Anhui Tingjian Technology Co ltd
Priority to CN202210851510.4A priority Critical patent/CN115292277A/en
Publication of CN115292277A publication Critical patent/CN115292277A/en
Pending legal-status Critical Current

Links

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/22—Indexing; Data structures therefor; Storage structures
    • G06F16/2282—Tablespace storage structures; Management thereof
    • 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/23—Updating
    • G06F16/2365—Ensuring data consistency and integrity

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Software Systems (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The method comprises the steps of firstly judging whether the total amount of data before migration and the total amount of data after migration are the same, if the total amount of data before migration and the total amount of data after migration are the same, further judging whether each piece of data is migrated according to a migration mapping rule corresponding to each piece of data, and if each piece of data is migrated according to the migration mapping rule corresponding to each piece of data, determining that the data before migration and the data after migration have consistency. By adopting the technical scheme, the data consistency before and after migration can be verified, the accuracy of data migration is ensured, the data consistency can be automatically verified, the verification speed is high, and manpower can be saved.

Description

Data migration consistency verification method, device, system, equipment and storage medium
Technical Field
The present application relates to the field of data processing technologies, and in particular, to a method, an apparatus, a system, a device, and a storage medium for verifying data migration consistency.
Background
Databases are collections of data that are stored together in a manner that can be shared with multiple users, have as little redundancy as possible, and are independent of applications. If the storage structure of the current database cannot meet the service requirement, the data in the database needs to be migrated to a new database which can meet the service requirement. After the data migration is completed, how to verify the data migration consistency and ensure the accuracy of the data migration is an urgent problem to be solved.
Disclosure of Invention
Based on the above requirements, the present application provides a method, an apparatus, a system, a device and a storage medium for verifying data migration consistency, where the method can verify data migration consistency and ensure accuracy of data migration.
The technical scheme provided by the application is as follows:
in one aspect, the present application provides a data migration consistency verification method, including:
judging whether the total data amount of the target data before migration is the same as the total data amount after migration;
if the total amount of the data before the migration is the same as the total amount of the data after the migration, judging whether the relation between the data before the migration and the data after the migration accords with a preset data migration mapping rule or not; the data migration mapping rule comprises a mapping relation between fields in the data table before migration and fields in the data table after migration;
and if the relationship between the data before the migration and the data after the migration conforms to the data migration mapping rule, determining that the data before the migration and the data after the migration are consistent.
Further, in the method described above, the target data includes a first type of data and a second type of data;
the judging whether the relationship between the data before the migration and the data after the migration meets the preset data migration mapping rule or not includes:
and respectively judging whether the first type of data and the second type of data before and after migration both accord with respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration accords with a preset data migration mapping rule based on the judgment result.
Further, in the above method, the respectively determining whether the first type of data and the second type of data before and after migration both conform to the respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration conforms to the preset data migration mapping rules based on the determination result includes:
judging whether the relation between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data;
if the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, judging whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data;
and if the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data, determining that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
Further, in the method described above, the method further includes:
if the relationship between the second type data before migration and the second type data after migration does not accord with the data migration mapping rule corresponding to the second type data, generating error prompt information of the second type data which is not migrated according to the corresponding data migration mapping rule, and determining that the relationship between the data before migration and the data after migration accords with the data migration mapping rule, or determining that the relationship between the data before migration and the data after migration does not accord with the data migration mapping rule.
Further, in the method described above, the determining whether the relationship between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data includes:
judging whether the relation between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration meets the data migration mapping rule corresponding to the first type of data;
and if the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data, determining that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
Further, in the method described above, if the data migration mapping rule is an equivalent migration mapping rule, the determining whether a relationship between a corresponding numerical value of the first type of data before the migration and a corresponding numerical value of the first type of data after the migration conforms to the data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to equal-quantity migration before migration is the same as the corresponding numerical value after migration;
if the corresponding numerical value of the first type of data subjected to the equal-amount migration before the migration is the same as the corresponding numerical value after the migration, determining that the relationship between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration accords with the data migration mapping rule corresponding to the first type of data.
Further, in the above method, if the data migration mapping rule is an unequal migration mapping rule, the determining whether a relationship between a value corresponding to the first type of data before the migration and a value corresponding to the first type of data after the migration meets the data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to unequal migration after migration is the corresponding numerical value before migration or not, and mapping the corresponding numerical value through the unequal migration mapping rule to obtain the numerical value;
if the value corresponding to the first type of data subjected to unequal migration after migration is obtained by mapping the value corresponding to the first type of data before migration according to the unequal migration mapping rule, determining that the relationship between the value corresponding to the first type of data before migration and the value corresponding to the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
Further, in the above method, before determining whether the total amount of data before migration and the total amount of data after migration are the same, the method further includes:
determining storage position information of target data before and after migration based on a preset data migration rule;
and reading the data before the migration and the data after the migration according to the storage position information of the target data before the migration and after the migration.
In another aspect, the present application provides a data migration consistency verification apparatus, including:
the first judgment module is used for judging whether the total data amount of the target data before migration is the same as the total data amount after migration;
the second judgment module is used for judging whether the relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule or not if the total amount of the data before migration is the same as the total amount of the data after migration; the data migration mapping rule comprises a mapping relation between fields in the data table before migration and fields in the data table after migration;
and the determining module is used for determining that the data before the migration and the data after the migration are consistent if the relationship between the data before the migration and the data after the migration conforms to the data migration mapping rule.
On the other hand, the present application provides an intelligent conference system, which is characterized by comprising:
the intelligent conference system comprises a server, an intelligent conference terminal and an intelligent display screen, wherein the intelligent conference terminal and the intelligent display screen are respectively connected with the server;
the server is used for storing data for supporting the intelligent conference terminal and the intelligent display screen to share the conference use duration;
when the intelligent conference terminal and/or the intelligent display screen migrate data to the server, the server judges whether the total data amount of the target data before migration is the same as the total data amount after migration; if the total amount of the data before migration is the same as the total amount of the data after migration, judging whether the relationship between the data before migration and the data after migration meets a preset data migration mapping rule or not, wherein the data migration mapping rule comprises the mapping relationship between fields in a data table before migration and fields in a data table after migration; and if the relationship between the data before migration and the data after migration conforms to the data migration mapping rule, determining that the data before migration and the data after migration are consistent.
In another aspect, the present application provides an electronic device, comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is configured to implement the data migration consistency verification method according to any one of the above items by running the program in the memory.
In another aspect, the present application provides a storage medium, comprising: the storage medium has stored thereon a computer program which, when executed by a processor, implements the steps of the data migration consistency verification method as described in any one of the above.
The data migration consistency verification method provided by the application judges whether the total amount of data before migration and the total amount of data after migration are the same, if the total amount of data before migration and the total amount of data after migration are the same, further judges whether each piece of data is migrated according to a migration mapping rule corresponding to each piece of data, and if each piece of data is migrated according to the migration mapping rule corresponding to each piece of data, determines that the data before migration and the data after migration have consistency. By adopting the technical scheme, the data consistency before and after migration can be verified, the accuracy of data migration is ensured, and moreover, the data consistency can be automatically verified, so that the verification speed is high, and manpower can be saved.
Drawings
In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below, it is obvious that the drawings in the following description are only embodiments of the present application, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic flowchart of a data migration consistency verification method according to an embodiment of the present application;
fig. 2 is a schematic flowchart illustrating a process of determining whether a relationship between data before migration and data after migration meets a data migration mapping rule according to an embodiment of the present application;
fig. 3 is a schematic flowchart of another process for determining whether a relationship between data before migration and data after migration meets a data migration mapping rule according to an embodiment of the present application;
fig. 4 is a schematic flowchart illustrating a process of determining whether a relationship between first-type data before migration and first-type data after migration meets a data migration mapping rule corresponding to the first-type data according to an embodiment of the present application;
fig. 5 is a flowchart illustrating a process of determining whether a relationship between first-type data before migration and first-type data after migration meets an equal-amount migration rule corresponding to the first-type data according to an embodiment of the present application;
fig. 6 is a schematic flowchart illustrating a process of determining whether a relationship between first-class data before migration and first-class data after migration meets an unequal migration rule corresponding to the first-class data according to the embodiment of the present application;
FIG. 7 is a schematic flowchart illustrating determining storage location information before and after target data migration according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a data migration consistency verification apparatus according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application;
fig. 10 is a schematic structural diagram of an intelligent conference system according to an embodiment of the present application.
Detailed Description
The technical scheme of the embodiment of the application is suitable for an application scene for verifying the data migration consistency, and by adopting the technical scheme of the embodiment of the application, the data consistency before and after migration can be automatically verified, so that the accuracy of data migration is ensured.
For example, the technical solution of the present application may be applied to hardware devices such as a hardware processor, or packaged into a software program to be executed, and when the hardware processor executes the processing procedure of the technical solution of the present application, or the software program is executed, the verification of the data migration consistency may be implemented. The embodiment of the present application only introduces the specific processing procedure of the technical scheme of the present application by way of example, and does not limit the specific execution form of the technical scheme of the present application, and any technical implementation form that can execute the processing procedure of the technical scheme of the present application may be adopted by the embodiment of the present application.
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment provides a data migration consistency verification method, and as shown in fig. 1, the method includes:
s101, judging whether the total data amount of the target data before migration is the same as the total data amount after migration; if the total amount of the target data before migration is the same as the total amount of the target data after migration, executing step S102; if the total amount of the target data before migration is different from the total amount of the target data after migration, step S104 is executed.
Migration refers to migrating data stored in one of the devices to another device, and target data refers to data undergoing migration. Specifically, if two devices are defined as device a and device b, the migration is to migrate data in device a to device b, or to migrate data in device b to device a, and the target data is to migrate data between device a and device b.
The device a and the device b are both devices having a storage unit, and the specific structure and type of the device a and the device b are not limited in this embodiment, for example, the device a and the device b may be devices such as an intelligent conference terminal, an intelligent display screen, a smart phone, a tablet computer, a server, or a memory. Moreover, the device a and the device b may be the same type of device or different types of devices, and this embodiment is not limited.
Illustratively, the target data may be migrated from device a to device b, which stores the target data, as follows:
and setting a data migration model so that the data migration model can learn the processing and storage mode of the equipment a for the data. Specifically, the device a may receive the data instruction, train the data migration model by using a processing process and a processing result executed by the device a based on the data instruction as a training sample, and adjust parameters of the data migration model according to the training result until the training result of the data migration model meets a preset requirement.
For example, some intelligent conference terminals and intelligent display screens give a certain conference duration quota when in sale, and when the intelligent conference terminals or the intelligent display screens are used for carrying out a video conference, the given conference duration quota is deducted according to the actual duration of the conference. If the conference time quota of the intelligent conference terminal and the intelligent display screen can be communicated, the intelligent conference terminal and the intelligent display screen can share the conference time quota of the other party, when one device is used for a video conference, the conference time quota of the other device can be deducted, and the time for the device to carry out the video conference is prolonged. If the conference duration quotas of the intelligent conference terminal and the intelligent display screen need to be communicated, the same server is needed to perform unified conference duration quota management on the intelligent conference terminal and the intelligent display screen.
If the server is used for carrying out unified conference duration quota management on the intelligent conference terminal and the intelligent display screen, the related data of the intelligent display screen is stored in the server, and the related data of the intelligent conference terminal is not stored in the server, the related data of the intelligent conference terminal needs to be migrated to the server. If the relevant data of the intelligent conference terminal in the above embodiment is migrated to the server, the data migration model needs to learn the deduction flow of the intelligent conference terminal, the quota flow of the conference time, the table structure corresponding to the data to be migrated, the table field, and the like.
In this embodiment, after the training of the data migration model is completed, a data table needs to be established in the migrated device, and the data migration model is further labeled.
Specifically, the migration in this embodiment includes three migration modes, which are 1-1 migration, 1-N migration, and M-N migration, where M and N are positive integers.
1-1 migration refers to the migration of the whole data table, and the data of the two tables before and after migration are in one-to-one correspondence. That is, for data subjected to 1-1 migration, how many pieces of data exist in the data table before migration corresponds to how many pieces of data exist in the data table after migration. In this embodiment, before migration, the data migration model needs to be further labeled, that is, for data before migration, which data needs to be migrated 1-1, and the storage location after migration is labeled, and if the data after migration and the data unit after migration are not consistent, the mapping rule corresponding to unit conversion needs to be labeled.
The 1-N migration refers to that one data table before migration is migrated to other equipment and then is split into a plurality of data tables, the data tables before and after migration do not have one-to-one correspondence, but the total data amount before and after migration is unchanged. In this embodiment, before migration, the data migration model needs to be further labeled, that is, for data before migration, which data needs to be subjected to 1-N migration, the storage positions of each split part after data migration are labeled, and if the data after migration and the data form after migration are inconsistent, the mapping rule corresponding to unit conversion needs to be labeled.
The M-N migration refers to that M data tables before migration are migrated to other equipment and then are split into N data tables, the data tables before and after migration do not have a one-to-one correspondence relationship, and the total data amount before and after migration is unchanged. In this embodiment, before migration, the data migration model needs to be further labeled, that is, for data before migration, which data needs to be subjected to M-N migration, splitting conditions of M data tables, and storage locations of split parts after data migration are labeled, and if the data after migration and the data table after migration are not in accordance, a mapping rule corresponding to unit conversion needs to be labeled.
In addition, some data before migration may be obsolete data, the obsolete data not only has no effect but also occupies a storage space, and then the part of data can be directly obsolete without being migrated. Therefore, in this embodiment, before migration, the data migration model needs to be further labeled, that is, for data before migration, which data is not migrated is labeled.
After the training and the labeling of the data migration model are finished, the data migration model can automatically migrate data according to the learned content and the labeled content. In this embodiment, the main purpose is to verify the data migration consistency, determine whether the data migration is accurately completed, and avoid the influence of data errors on subsequent links.
Based on the data migration model or the labeled content for the data before migration, the storage location information of each item of data before migration and the storage location information of each item of data after migration can be determined in this embodiment. If the data in the device a is migrated to the device b, based on the storage location information of each item of data before migration and the storage location information of each item of data after migration, the embodiment can capture the data before migration from the device a, capture the corresponding data after migration from the device b, compare and check the data before migration and the corresponding data after migration, and determine whether the data before migration and the data after migration are consistent.
In the embodiment of the present application, in order to improve the verification efficiency, it is first determined whether the total amount of the target data before migration is the same as the total amount of the target data after migration.
Specifically, if the data in the device a is migrated to the device b in this embodiment, the total amount of the target data before migration may be calculated from the device a, the total amount of the target data after migration may be calculated from the device b, and then whether the total amount of the target data before migration is the same as the total amount of the target data after migration is compared. If the total amount of data before migration is the same as the total amount of data after migration, step S102 needs to be executed; if the total amount of data before migration is different from the total amount of data after migration, step S104 needs to be executed.
S102, judging whether the relation between the data before migration and the data after migration accords with a preset data migration mapping rule or not, if so, executing a step S103, and if not, executing a step S104.
The data migration mapping rule includes a mapping relationship between a field in the data table before migration and a field in the data table after migration, and the data migration mapping rule in this embodiment includes an equal-amount migration mapping rule and a non-equal-amount migration mapping rule.
The equivalent migration mapping rule indicates that the field in the data table before migration is the same as the field in the data table after migration, and if the data in the device a is migrated to the device b in this embodiment, the data in the device a is directly mapped to the device b in a ratio of 1: 1 according to the equivalent migration rule.
The unequal migration mapping rule indicates that the fields in the data table before migration are different from the fields in the data table after migration, but a certain mapping relationship exists between the fields, and if the data in the device a is migrated to the device b in this embodiment, according to the unequal migration rule, the data in the device b is obtained by mapping the data of the device a according to the mapping relationship between the data and the device b. For example, if the unit used when the device a stores time is hour, and the unit representing time needs to be modified into minute when the data in the device a is migrated to the device b, then the part of the data corresponds to time, and mapping of time conversion is needed when the migration is performed, and the data in the device b is obtained after the data in the device a is subjected to the mapping processing from hour to minute.
In most cases, when migrating data in the device a to the device b, data migrated according to the equal migration rule and data migrated according to the unequal migration rule exist in all target data to be migrated at the same time, and different unequal migration rules may be followed in the data migrated according to the unequal migration rule.
Based on the data migration model or the labeled content for the pre-migration data, the storage location information of each item of data before migration, the storage location information of each item of data after migration, and the mapping rule that each item of data needs to follow can be determined in this embodiment.
If the present embodiment is to migrate data in the device a to the device b, based on the storage location information of each item of data before migration and the storage location information of each item of data after migration, the present embodiment can capture the data before migration from the device a, and further verify whether a relationship between the data before migration and the data after migration conforms to a mapping rule that each item of data needs to follow after verifying that the total amount of data before migration and the total amount of data after migration of the target data are the same, that is, verify whether a relationship between the data before migration and the data after migration conforms to the data migration mapping rule. If the relationship between the data before migration and the data after migration conforms to the data migration mapping rule, step S103 may be executed; if the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule, step S104 may be executed.
And S103, determining that the data before migration and the data after migration are consistent.
If the total amount of data before migration is the same as the total amount of data after migration, and the relationship between the data before migration and the data after migration conforms to the data migration mapping rule, it is determined that the data before migration and the data after migration are consistent, the data migration is successful, and the consistency verification of this embodiment is finished.
And S104, determining that the data before and after the migration are inconsistent.
If the total amount of the data before migration is the same as the total amount of the data after migration, but the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule, or the total amount of the data before migration is different from the total amount of the data after migration, it is determined that the data before migration and the data after migration are inconsistent, the data migration fails, and the consistency verification in this embodiment is finished.
The manual verification method widely adopted in the prior art has the advantages that the efficiency, the low time consumption and the low accuracy are realized, the verification can only be carried out on the migration quantity, the accuracy requirement of data migration cannot be met, and the verification tools such as oracle and Navicat are only suitable for simple data migration such as 1-1 migration, so that the application range is small. In the above embodiments provided by the present application, it is first determined whether the total amount of data before migration and the total amount of data after migration are the same, and if the total amount of data before migration and the total amount of data after migration are the same, it is further determined whether each piece of data is migrated according to the migration mapping rule corresponding to each piece of data, and if each piece of data is migrated according to the migration mapping rule corresponding to each piece of data, it is determined that the data before migration and the data after migration have consistency. By adopting the technical scheme, the consistency of the data before and after the migration can be verified, and the accuracy of the data migration is further ensured. Moreover, the data consistency can be automatically verified, the verification speed is high, and labor can be saved.
As an optional implementation manner, another embodiment of the present application discloses that the step of the foregoing embodiment determines whether the relationship between the data before migration and the data after migration meets a preset data migration mapping rule, and specifically may include the following steps:
and respectively judging whether the first type of data and the second type of data before and after migration both accord with respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration accords with a preset data migration mapping rule based on the judgment result.
The target data includes a first type of data and a second type of data. In this embodiment, the first type of data refers to key data that affects program operation or has a large effect on the entire business process in the target data, and the second type of data refers to non-key data that does not affect program operation and does not affect the entire business process. The critical data and the non-critical data in different types of devices are not the same, and those skilled in the art may set the first type of data and the second type of data according to actual situations, which is not limited in this embodiment.
It should be noted that the first type of data may include data migrated according to an equal migration rule and data migrated according to an unequal migration rule, or may include only data migrated according to an equal migration rule or only data migrated according to an unequal migration rule, and if there is data migrated according to an unequal migration rule in the first type of data, the unequal migration rules adopted by the data migrated according to the unequal migration rule may also be different; the second type of data may include data migrated according to an equal migration rule and data migrated according to an unequal migration rule, or may only include data migrated according to an equal migration rule or only include data migrated according to an unequal migration rule, and if there is data migrated according to an unequal migration rule in the second type of data, the unequal migration rules used for the data migrated according to the unequal migration rule may not be the same, which is not limited in this embodiment.
In this embodiment, it is respectively determined whether the first type of data and the second type of data before and after migration both conform to the respective corresponding data migration mapping rules. Specifically, in this embodiment, it is determined that the relationship between the first type of data before migration and the first type of data after migration conforms to a migration mapping rule corresponding to the first type of data; judging whether the relationship between the second type data before migration and the second type data after migration conforms to the migration mapping rule corresponding to the second type data, and comprehensively determining whether the relationship between the data before migration and the data after migration conforms to the preset data migration mapping rule according to the obtained judgment result.
For example, if the first type of data and the second type of data both conform to the respective corresponding data migration mapping rules, it indicates whether the relationship between the data before migration and the data after migration conforms to the preset data migration mapping rules.
For another example, the second type of data corresponds to non-critical data, and the second type of data may not cause any impact if the migration is wrong. Therefore, in this embodiment, the requirement on the second type of data is relaxed, and when all the relationships between the first type of data before migration and the first type of data after migration conform to the migration mapping rule corresponding to the first type of data, if there is a portion of the relationships between the second type of data before migration and the second type of data after migration that do not conform to the migration mapping rule corresponding to the second type of data, an error prompt may be performed only for the second type of data that is not migrated according to the corresponding data migration mapping rule, and it is determined that the relationship between the data before migration and the data after migration conforms to the preset data migration mapping rule.
For another example, the second type of data corresponds to non-critical data, and the second type of data may not cause any impact if the migration is wrong. Therefore, in order to save time in this embodiment, migration consistency verification is performed only on the first type of data, and migration consistency of the second type of data is not verified any more. And when the relationship between all the first type data before migration and the first type data after migration conforms to the migration mapping rule corresponding to the first type data, determining that the relationship between the data before migration and the data after migration conforms to the preset data migration mapping rule.
In this embodiment, migration consistency verification is automatically performed according to data migration mapping rules corresponding to different types of data, so that accuracy of data migration can be ensured.
As an optional implementation manner, as shown in fig. 2, another embodiment of the present application discloses that the steps of the foregoing embodiment respectively determine whether the first type of data and the second type of data before and after migration both conform to respective corresponding data migration mapping rules, and determine whether a relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule based on a result of the determination, and specifically may include the following steps:
s201, judging whether the relation between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data; if the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, executing step S202; if the relationship between the first type of data before migration and the first type of data after migration does not conform to the data migration mapping rule corresponding to the first type of data, step S204 is executed.
Since the first type of data is the key data, in the embodiment of the application, it is preferentially determined whether the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
The first type of data may include data migrated according to an equal migration rule and data migrated according to a non-equal migration rule, or may include only data migrated according to an equal migration rule and only data migrated according to a non-equal migration rule. Also, the unequal migration rules may include a variety of different rules, such as time unit conversion, distance unit conversion, and the like.
In the embodiment of the application, when the migration consistency of the first type of data is judged, data adopting different migration rules in the first type of data are verified one by one according to the corresponding migration rules, and whether the relationship between the first type of data before migration and the first type of data after migration meets the data migration mapping rule corresponding to the first type of data is determined based on the verification result.
Illustratively, if the first type of data includes a data set a migrated according to an equivalent migration rule and a data set B migrated according to an unequal migration rule, the data set B migrated according to the unequal migration rule includes a data subset B1 converted according to a time unit and a data subset B2 converted according to a distance unit, when migration consistency verification is performed on the first type of data, it is verified whether data corresponding to the data set a before migration and data corresponding to the data after migration conform to the equivalent migration rule, it is verified whether data corresponding to the data set B1 before migration and data corresponding to the data after migration conform to a rule converted according to a time unit in the unequal migration rule, it is verified whether data corresponding to the data set B2 before migration and data corresponding to the data after migration conform to a rule converted according to a distance unit in the unequal migration rule, if both of the rules conform, it indicates that a relationship between the first type of data before migration and the first type of data after migration conforms to a data migration mapping rule corresponding to the first type of data before migration, and if at least one piece of data does not conform to the mapping relationship between the first type of data before migration and the first type of data after migration.
In this embodiment, if it is determined that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, step S202 is executed; if it is determined that the relationship between the first type of data before migration and the first type of data after migration does not conform to the data migration mapping rule corresponding to the first type of data, step 204 is executed.
S202, judging whether the relation between the second type data before migration and the second type data after migration meets a data migration mapping rule corresponding to the second type data or not; if the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data, executing step S203; if the relationship between the second type data before migration and the second type data after migration does not conform to the data migration mapping rule corresponding to the second type data, generating an error prompt message for the second type data which is not migrated according to the corresponding data migration mapping rule, and executing step S203.
After determining that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, further judging whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data.
The second type of data may include data migrated according to an equal migration rule and data migrated according to an unequal migration rule, or may include only data migrated according to an equal migration rule and only data migrated according to an unequal migration rule. Also, the unequal migration rules may include a variety of different rules, such as time unit conversion, distance unit conversion, and the like.
In the embodiment of the application, when the migration consistency of the second type data is judged, data adopting different migration rules in the second type data are verified one by one according to the corresponding migration rules, and whether the relationship between the second type data before migration and the second type data after migration meets the data migration mapping rule corresponding to the second type data is determined based on the verification result.
Illustratively, if the second type of data includes a data set C migrated according to an equivalent migration rule and a data set D migrated according to an unequal migration rule, the data set D migrated according to the unequal migration rule includes a data subset D1 converted according to a time unit and a data subset D2 converted according to a distance unit, when performing migration consistency verification on the second type of data, it is verified whether corresponding data before migration of the data set C and corresponding data after migration conform to the equivalent migration rule, it is verified whether corresponding data before migration of the data set D1 and corresponding data after migration conform to a rule converted according to a time unit in the unequal migration rule, it is verified whether corresponding data before migration of the data set D2 and corresponding data after migration conform to a rule converted according to a distance unit in the unequal migration rule, if both conform, it indicates that a relationship between the second type of data before migration and the second type of data after migration conforms to a data migration rule corresponding to the second type of data, and if at least one piece of data does not conform to a second type of data mapping rule corresponding to a second type of data after migration.
In this embodiment, if it is determined that both the first type of data and the second type of data before and after migration conform to the respective corresponding data migration mapping rules, step S203 is executed to determine that the relationship between the data before migration and the data after migration conforms to the respective corresponding data migration mapping rules; if the first type of data before and after migration is determined to accord with the data migration mapping rule corresponding to the first type of data, and the second type of data before and after migration does not accord with the data migration mapping rule corresponding to the second type of data, generating error prompt information of the second type of data which is not migrated according to the corresponding data migration mapping rule, and executing step S203.
The error prompt information refers to error prompt information of second-class data that is not migrated according to the corresponding data migration mapping rule, and the error prompt information may be output in a text form or in a sound form, which is not limited in this embodiment. The error notification information may be a simplified information, for example, only including the name of the error data, or may be a detailed information, for example, including the name of the error data, the specific error content, the migration time of the data, and the like, and the embodiment is not limited thereto.
In this embodiment, the second type of data corresponds to non-critical data, and if an error occurs in the migration of the second type of data, no influence may be caused. Therefore, in the embodiment of the application, the second type data is not required to be completely and accurately migrated, and only the second type data with the migration error needs to be recorded.
S203, determining that the relationship between the data before the migration and the data after the migration accords with a data migration mapping rule.
If the first type of data and the second type of data before and after migration are determined to accord with the respective corresponding data migration mapping rules, determining that the relationship between the data before migration and the data after migration accords with the data migration mapping rules; or, if it is determined that the first type of data before and after migration conforms to the data migration mapping rule corresponding to the first type of data and the second type of data before and after migration does not conform to the data migration mapping rule corresponding to the second type of data, error prompt information of the second type of data that is not migrated according to the corresponding data migration mapping rule may be generated and it is determined that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
In another embodiment, in order to improve the data migration verification speed, the migration consistency verification may not be performed on the second type of data, and only the migration consistency of the first type of data is verified, in such a case, if it is determined that the first type of data before and after migration conforms to the data migration mapping rule corresponding to the first type of data, it is determined that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
S204, determining that the relationship between the data before migration and the data after migration does not accord with the data migration mapping rule.
In this embodiment, if it is determined that the first type of data before and after migration does not conform to the data migration mapping rule corresponding to the first type of data, it is determined that the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule, the data before migration and the data after migration are not consistent, the data migration fails, and the consistency verification of this embodiment is finished.
In the embodiment of the application, the migration consistency verification is preferentially performed on the critical first-class data, the migration consistency of the non-critical second-class data is verified after the first-class data has the migration consistency, and the migration failure is determined when the first-class data does not have the migration consistency, so that the verification efficiency can be effectively improved by performing the step-by-step migration verification.
As an alternative implementation, as shown in fig. 3, in another embodiment of the present application, it is disclosed that the steps of the above embodiment further include:
s301, judging whether the relation between the first type data before migration and the first type data after migration accords with a data migration mapping rule corresponding to the first type data; if the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, executing step S302; if the relationship between the first type of data before migration and the first type of data after migration does not conform to the data migration mapping rule corresponding to the first type of data, step S304 is executed.
S302, judging whether the relationship between the second type data before migration and the second type data after migration meets a data migration mapping rule corresponding to the second type data; if the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data, executing step S303; if the relationship between the second type of data before migration and the second type of data after migration does not conform to the data migration mapping rule corresponding to the second type of data, step S304 is executed.
S303, determining that the relationship between the data before the migration and the data after the migration accords with a data migration mapping rule.
S304, determining that the relationship between the data before migration and the data after migration does not accord with the data migration mapping rule.
In this embodiment, the steps of determining whether the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data and determining whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data are the same as the steps in the above embodiments, and those skilled in the art may refer to the descriptions in the above embodiments, which are not described herein again.
It should be noted that, in the embodiment of the present application, after it is determined that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, and it is determined that the relationship between the second type of data before migration and the second type of data after migration does not conform to the data migration mapping rule corresponding to the second type of data, it is determined that the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule.
Specifically, if the requirement on the migration consistency of the second type data is high in the migration process of the data, and it is necessary to ensure that the migration of the second type data is also completely correct, after it is determined that the relationship between the second type data before migration and the second type data after migration does not conform to the data migration mapping rule corresponding to the second type data, it is determined that the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule, the data before migration and the data after migration are not consistent, the data migration fails, and the consistency verification in this embodiment is finished.
In the embodiment of the application, the migration consistency verification is preferentially performed on the critical first-class data, the migration consistency of the non-critical second-class data is verified after the first-class data has the migration consistency, and the migration failure is determined when the first-class data and the second-class data do not have the migration consistency, so that all data migration can be ensured to be correct by performing the step-by-step migration verification, and the reliability of the consistency verification result is improved.
As an optional implementation manner, as shown in fig. 4, another embodiment of the present application discloses that the step of the foregoing embodiment judges whether the relationship between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data, and specifically may include the following steps:
s401, judging whether the relation between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration meets the data migration mapping rule corresponding to the first type of data; if the relationship between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration meets the data migration mapping rule corresponding to the first type of data, executing step S402; if the relationship between the corresponding value of the first type of data before migration and the corresponding value after migration does not conform to the data migration mapping rule corresponding to the first type of data, step S403 is executed.
In this embodiment, whether the relationship between the value corresponding to the first type of data before migration and the value corresponding to the first type of data after migration meets the data migration mapping rule corresponding to the first type of data is determined, and whether the relationship between the first type of data before migration and the first type of data after migration meets the data migration mapping rule corresponding to the first type of data is determined based on the determination result.
Specifically, whether a numerical value corresponding to data to be migrated according to an equivalent migration rule in the first data meets the equivalent migration rule before and after migration is judged; and judging whether the numerical value corresponding to the data migrated according to the unequal amount migration rule in the first data meets the corresponding unequal amount migration rule before and after migration.
Illustratively, if the first type of data includes a data set a migrated according to an equal migration rule and a data set B migrated according to an unequal migration rule, and the data set B migrated according to the unequal migration rule includes a data subset B1 converted according to a time unit and a data subset B2 converted according to a distance unit, when it is determined whether a relationship between a value corresponding to the first type of data before migration and a value corresponding to the first type of data after migration conforms to a data migration mapping rule corresponding to the first type of data, it is determined whether a value corresponding to data in the data set a before migration and after migration conforms to an equal migration rule in the unequal migration rule, it is determined whether a value corresponding to data in the data set B1 before migration and after migration conforms to a rule converted according to a time unit in the unequal migration rule, and it is determined whether a value corresponding to data in the data set B2 before migration and after migration conforms to a rule converted according to a distance unit in the unequal migration rule.
If the relationship between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration meets the data migration mapping rule corresponding to the first type of data after the judgment, executing the step S402; if the relationship between the corresponding value of the first type of data before migration and the corresponding value after migration does not conform to the data migration mapping rule corresponding to the first type of data, step S403 is executed.
S402, determining that the relation between the first type of data before migration and the first type of data after migration accords with a data migration mapping rule corresponding to the first type of data.
In this step, if it is determined that the relationship between the value corresponding to the first type of data before migration and the value corresponding to the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data after judgment, it is determined that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
S403, determining that the relationship between the first type of data before migration and the first type of data after migration does not accord with the data migration mapping rule corresponding to the first type of data.
If the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration does not conform to the data migration mapping rule corresponding to the first type of data, it is determined that the relationship between the first type of data before migration and the first type of data after migration does not conform to the data migration mapping rule corresponding to the first type of data, and it is further determined that the relationship between the data before migration and the data after migration does not conform to the preset data migration mapping rule, the data before migration and the data after migration are not consistent, the data migration fails, and the consistency verification of the embodiment is finished.
In this embodiment, whether the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data is determined based on whether the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data, so that the consistency of the data before migration and the data after migration can be effectively verified.
As an optional implementation manner, as shown in fig. 5, in another embodiment of the present application, it is disclosed that, if the data migration mapping rule is an equivalent migration mapping rule, the steps of the foregoing embodiment determine whether a relationship between a corresponding numerical value of the first type of data before the migration and a corresponding numerical value after the migration meets the data migration mapping rule corresponding to the first type of data, and specifically may include the following steps:
s501, judging whether the corresponding numerical value of the first type data subjected to equal-quantity migration before migration is the same as the corresponding numerical value after migration; if the corresponding numerical value of the first type data subjected to the equal-amount migration before the migration is the same as the corresponding numerical value after the migration, executing S502; if the corresponding value of the first type data subjected to the equal amount of migration before the migration is different from the corresponding value after the migration, S503 is executed.
In this embodiment, when the data migration mapping rule is the equivalent migration mapping rule, it is determined whether the corresponding value of the first type of data subjected to the equivalent migration before the migration is the same as the corresponding value after the migration. For example, if there is a piece of data of the first type subjected to equal migration, and the corresponding value before the migration is 100, and the corresponding value after the migration is still 100, it indicates that the corresponding value before the migration is the same as the corresponding value after the migration.
If the corresponding numerical value of each first type of data subjected to equal-amount migration before the migration is the same as the corresponding numerical value after the migration, executing S502; if at least one piece of first-class data subjected to equal-amount migration has a corresponding numerical value before migration and a corresponding numerical value after migration which are different, S503 is executed.
S502, determining that the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration accords with the data migration mapping rule corresponding to the first type of data.
In this embodiment, if the corresponding numerical value of each piece of first-class data subjected to equal-amount migration before the migration is the same as the corresponding numerical value after the migration, it indicates that the relationship between the corresponding numerical value of the first-class data before the migration and the corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the first-class data.
S503, determining that the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration does not conform to the data migration mapping rule corresponding to the first type of data.
In this embodiment, if there is at least one value corresponding to the first type of data subjected to equal amount of migration before the migration and the value corresponding to the first type of data after the migration are different, it indicates that a relationship between the value corresponding to the first type of data before the migration and the value corresponding to the first type of data after the migration does not conform to a data migration mapping rule corresponding to the first type of data, and further may determine that the relationship between the first type of data before the migration and the first type of data after the migration does not conform to a data migration mapping rule corresponding to the first type of data, and then determine that the relationship between the data before the migration and the data after the migration does not conform to a preset data migration mapping rule, the data before the migration and the data after the migration are not consistent, the data migration fails, and the consistency verification in this embodiment is completed.
In this embodiment, when the data migration mapping rule is an equivalent migration mapping rule, it is determined whether a relationship between a value corresponding to the first type of data before migration and a value corresponding to the first type of data after migration matches the data migration mapping rule corresponding to the first type of data based on whether a value corresponding to the first type of data before migration and a value corresponding to the first type of data after migration are the same, and the consistency of the data before migration and the data after migration can be effectively verified.
As an optional implementation manner, as shown in fig. 6, another embodiment of the present application discloses that, if the data migration mapping rule is a non-equivalent migration mapping rule, the steps of the foregoing embodiment determine whether a relationship between a corresponding numerical value of the first type of data before migration and a corresponding numerical value after migration matches the data migration mapping rule corresponding to the first type of data, which may specifically include the following steps:
s601, judging whether the corresponding numerical value of the first type of data subjected to unequal amount migration after migration is obtained by mapping the corresponding numerical value before migration according to an unequal amount migration mapping rule; if the corresponding numerical value of the first type of data subjected to unequal amount migration after migration is obtained by performing mapping processing on the corresponding numerical value before migration through an unequal amount migration mapping rule, executing step S602; if the value corresponding to the first type of data subjected to unequal amount migration after migration is not obtained by performing mapping processing on the corresponding value before migration according to the unequal amount migration mapping rule, step S603 is executed.
In this embodiment, when the data migration mapping rule is the unequal migration mapping rule, it is determined whether the corresponding value of the first type of data subjected to unequal migration after migration is the corresponding value before migration and is obtained by performing mapping processing according to the unequal migration mapping rule. For example, if there is a piece of first-type data to be migrated with unequal amount, and the unequal amount migration mapping rule includes a time unit conversion rule, specifically, an hour is converted into a minute, a corresponding numerical value before migration is 2, and a corresponding numerical value after migration is 120, it may be determined that the corresponding numerical value after migration is obtained by mapping the corresponding numerical value before migration through the time unit conversion rule.
It should be noted that the unequal migration mapping rules may include various different migration rules, and in the verification in this embodiment, the verification is performed based on the mapping rule corresponding to each piece of the first type data subjected to unequal migration. If the corresponding numerical value of each first type of data subjected to unequal migration after migration is obtained by mapping the corresponding numerical value before migration according to an unequal migration mapping rule, executing S602; if at least one first-class data subjected to equal-amount migration is obtained by performing mapping processing on a value corresponding to the migrated first-class data after migration and a value corresponding to the migrated first-class data before migration through a non-equal-amount migration mapping rule, S603 is executed.
S602, determining that the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data.
And if the numerical value corresponding to each piece of the first-class data subjected to unequal migration after migration is obtained by mapping the corresponding numerical value before migration through an unequal migration mapping rule, determining that the relationship between the corresponding numerical value of the first-class data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first-class data.
S603, determining that the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration accords with the data migration mapping rule corresponding to the first type of data.
If there is at least one value corresponding to the first type of data subjected to equal-amount migration after the migration is not the value corresponding to the first type of data before the migration and is obtained by performing mapping processing through a non-equal-amount migration mapping rule, it is determined that the relationship between the value corresponding to the first type of data before the migration and the value corresponding to the first type of data after the migration does not conform to the data migration mapping rule corresponding to the first type of data, it may be further determined that the relationship between the first type of data before the migration and the first type of data after the migration does not conform to the data migration mapping rule corresponding to the first type of data, it is further determined that the relationship between the data before the migration and the data after the migration does not conform to the preset data migration mapping rule, the data before the migration and the data after the migration are not consistent, the data migration fails, and the consistency verification of this embodiment is finished.
In this embodiment, under the condition that the data migration mapping rule is the unequal amount migration mapping rule, it is determined whether the relationship between the corresponding value of the first type of data before migration and the corresponding value of the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data according to whether the corresponding value of the first type of data after migration is the corresponding value before migration and is obtained by performing mapping processing according to the unequal amount migration mapping rule, so that the consistency of the data before migration and after migration can be effectively verified.
As an optional implementation manner, another embodiment of the present application discloses that the step of determining whether the relationship between the second type of data before migration and the second type of data after migration meets the data migration mapping rule corresponding to the second type of data includes:
judging whether the relation between the corresponding numerical value of the second type data before the migration and the corresponding numerical value after the migration meets the data migration mapping rule corresponding to the second type data or not;
and if the relationship between the corresponding numerical value of the second type data before the migration and the corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the second type data, determining that the relationship between the second type data before the migration and the second type data after the migration conforms to the data migration mapping rule corresponding to the second type data.
As an optional implementation manner, another embodiment of the present application discloses that, if the data migration mapping rule is an equivalent migration mapping rule, the steps of the above embodiment determine whether a relationship between a corresponding numerical value of the second type of data before the migration and a corresponding numerical value after the migration meets the data migration mapping rule corresponding to the second type of data, and specifically may include the following steps:
judging whether the corresponding numerical value of the second type data subjected to the equal-quantity migration before the migration is the same as the corresponding numerical value after the migration;
and if the corresponding numerical value of the second type data subjected to equal-quantity migration before the migration is the same as the corresponding numerical value after the migration, determining that the relationship between the corresponding numerical value of the second type data before the migration and the corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the second type data.
As an optional implementation manner, in another embodiment of the present application, it is disclosed that, if the data migration mapping rule is an unequal amount migration mapping rule, the step of the above embodiment of determining whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data includes:
judging whether the corresponding numerical value of the second type data subjected to unequal migration after migration is the corresponding numerical value before migration or not, and mapping the corresponding numerical value through an unequal migration mapping rule to obtain the numerical value;
and if the numerical value corresponding to the second type of data subjected to unequal amount migration after migration is obtained by mapping the numerical value corresponding to the second type of data before migration through an unequal amount migration mapping rule, determining that the relationship between the numerical value corresponding to the second type of data before migration and the numerical value corresponding to the second type of data after migration accords with the data migration mapping rule corresponding to the second type of data.
When performing migration consistency verification on the second type of data, the specific verification steps are the same as the steps of performing migration consistency verification on the first type of data in the above embodiment, and the same beneficial effects can be produced.
As an optional implementation manner, as shown in fig. 7, another embodiment of the present application discloses that before the steps of the foregoing embodiment determine whether the total amount of data before migration and the total amount of data after migration are the same, the following steps may also be included:
s701, determining storage position information of the target data before and after migration based on a preset data migration rule.
The preset data migration rule includes the data migration model of the above embodiment or the labeling content for the data before migration. Specifically, because information such as a migration position and a mapping rule for data before migration is labeled in the data migration model in advance, in the embodiment of the present application, storage position information of target data before migration and after migration and a data migration mapping rule corresponding to the target data may be determined based on the data migration model; in addition, the storage location information of the target data before and after migration and the data migration mapping rule corresponding to the target data may be determined based on the labeled content for the data before migration, which is not limited in this embodiment.
It should be noted that, the above labeling performed on the model may be manually performed by a human, or a labeling model is used for labeling, which is not limited in this embodiment.
If the data in the device a is migrated to the device b in this embodiment, the storage location information refers to a storage location of the data before migration in the device a and a storage location of the data after migration in the device b.
S702, reading the data before migration and the data after migration according to the storage position information of the target data before and after migration.
In this embodiment, after determining the storage location information of the target data before and after migration, the data before migration and the data after migration may be read based on the storage location information of the target data before and after migration, so as to verify the consistency of the target data before and after migration.
In the embodiment of the application, the storage position information of the target data before and after migration is determined based on a preset data migration rule, so that data corresponding to the target data before and after migration can be extracted, and consistency of the target data before and after migration can be verified.
As an optional implementation manner, in another embodiment of the present application, it is disclosed that the calculation speed of the data migration consistency verification method in the above embodiment is detected, and if the calculation speed is slow in an actual verification process, an operation script corresponding to the data migration consistency verification method needs to be optimized, so that the compression verification time is preferably within 30 minutes.
Corresponding to the above data migration consistency verification method, an embodiment of the present application further discloses a data migration consistency verification apparatus, as shown in fig. 8, the apparatus includes:
a first determining module 100, configured to determine whether a total amount of data of the target data before migration is the same as a total amount of data after migration;
a second determining module 110, configured to determine whether a relationship between the data before migration and the data after migration meets a preset data migration mapping rule if the total amount of the data before migration is the same as the total amount of the data after migration; the data migration mapping rule comprises a mapping relation between fields in the data table before migration and fields in the data table after migration;
the determining module 120 is configured to determine that the data before the migration and the data after the migration are consistent if a relationship between the data before the migration and the data after the migration conforms to a data migration mapping rule.
Optionally, in another embodiment of the present application, the target data includes a first type of data and a second type of data;
when the second determining module 110 determines whether the relationship between the data before migration and the data after migration meets the preset data migration mapping rule, it is specifically configured to:
and respectively judging whether the first type of data and the second type of data before and after migration both accord with respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration accords with a preset data migration mapping rule based on the judgment result.
Optionally, in another embodiment of the present application, the second determining module 110 includes:
the first judging unit is used for judging whether the relation between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data;
the second judging unit is used for judging whether the relationship between the second type of data before migration and the second type of data after migration accords with the data migration mapping rule corresponding to the second type of data or not if the relationship between the first type of data before migration and the first type of data after migration accords with the data migration mapping rule corresponding to the first type of data;
the first determining unit is configured to determine that the relationship between the pre-migration data and the post-migration data conforms to the data migration mapping rule if the relationship between the pre-migration second type data and the post-migration second type data conforms to the data migration mapping rule corresponding to the second type data.
Optionally, in another embodiment of the present application, the second determining module 110 further includes:
and the second determining unit is used for generating error prompt information of the second type data which is not migrated according to the corresponding data migration mapping rule and determining that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule or determining that the relationship between the data before migration and the data after migration does not conform to the data migration mapping rule if the relationship between the second type data before migration and the second type data after migration does not conform to the data migration mapping rule corresponding to the second type data.
Optionally, in another embodiment of the present application, the first determining unit, when determining whether a relationship between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data, is specifically configured to:
judging whether the relation between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration meets the data migration mapping rule corresponding to the first type of data;
and if the relationship between the corresponding numerical value of the first type data before the migration and the corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the first type data, determining that the relationship between the first type data before the migration and the first type data after the migration conforms to the data migration mapping rule corresponding to the first type data.
Optionally, in another embodiment of the present application, the first determining unit includes:
the first judgment subunit is used for judging whether the corresponding numerical value of the first type of data subjected to equal-quantity migration before migration is the same as the corresponding numerical value after migration;
the first determining subunit is configured to determine that a relationship between a corresponding numerical value of the first type of data before migration and a corresponding numerical value of the first type of data after migration conforms to a data migration mapping rule corresponding to the first type of data if the corresponding numerical value of the first type of data before migration and the corresponding numerical value of the first type of data after migration are the same.
Optionally, in another embodiment of the present application, the first determining unit further includes:
the second judgment subunit is used for judging whether the corresponding numerical value of the first type of data subjected to unequal migration after migration is the corresponding numerical value before migration and is obtained by mapping the corresponding numerical value through an unequal migration mapping rule;
and the second determining subunit is configured to determine that a relationship between a value corresponding to the first type of data before migration and a value corresponding to the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data if the value corresponding to the first type of data after migration in an unequal amount is obtained by mapping the corresponding value before migration according to the unequal amount migration mapping rule.
Optionally, in another embodiment of the present application, the method further includes:
the position determining module is used for determining the storage position information of the target data before and after migration based on a preset data migration rule before judging whether the total amount of the data before and after migration is the same;
and the reading module is used for reading the data before the migration and the data after the migration according to the storage position information of the target data before the migration and after the migration.
Specifically, please refer to the contents of the above method embodiments for the specific working contents of each unit of the data migration consistency verification apparatus, which are not described herein again.
Another embodiment of the present application further provides an electronic device, as shown in fig. 9, the electronic device including:
a memory 200 and a processor 210;
wherein, the memory 200 is connected with the processor 210 for storing programs;
the processor 210 is configured to implement the data migration consistency verification method disclosed in any of the above embodiments by executing the program stored in the memory 200.
Specifically, the electronic device may further include: a bus, a communication interface 220, an input device 230, and an output device 240.
The processor 210, the memory 200, the communication interface 220, the input device 230, and the output device 240 are connected to each other through a bus. Wherein:
a bus may include a path that transfers information between components of a computer system.
The processor 210 may be a general-purpose processor, such as a general-purpose Central Processing Unit (CPU), microprocessor, etc., an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of programs in accordance with the present disclosure. But may also be a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components.
The processor 210 may include a main processor and may also include a baseband chip, a modem, and the like.
The memory 200 stores programs for executing the technical solution of the present application, and may also store an operating system and other key services. In particular, the program may include program code including computer operating instructions. More specifically, memory 200 may include read-only memory (ROM), other types of static storage devices that may store static information and instructions, random Access Memory (RAM), other types of dynamic storage devices that may store information and instructions, disk storage, flash, and the like.
The input device 230 may include a means for receiving data and information input by a user, such as a keyboard, mouse, camera, scanner, light pen, voice input device, touch screen, pedometer, or gravity sensor, among others.
Output device 240 may include equipment that allows output of information to a user, such as a display screen, printer, speakers, etc.
Communication interface 220 may include any device that uses any transceiver or the like to communicate with other devices or communication networks, such as an ethernet network, a Radio Access Network (RAN), a Wireless Local Area Network (WLAN), etc.
The processor 210 executes the program stored in the memory 200 and invokes other devices, which can be used to implement the steps of the data migration consistency verification method provided by the above-described embodiment of the present application.
Another embodiment of the present application further provides an intelligent conference system. Referring to fig. 10, the intelligent conference system includes:
a server 300, and an intelligent conference terminal 310 and an intelligent display screen 320 respectively connected to the server 300;
the server 300 is configured to store data supporting the intelligent conference terminal 310 and the intelligent display screen 320 to share the conference use duration;
when the intelligent conference terminal 310 and/or the intelligent display screen 320 migrate data to the server 300, the server 300 determines whether the total amount of the target data before migration is the same as the total amount of the target data after migration; if the total amount of the data before the migration is the same as the total amount of the data after the migration, judging whether the relation between the data before the migration and the data after the migration accords with a preset data migration mapping rule or not, wherein the data migration mapping rule comprises the mapping relation between fields in a data table before the migration and fields in a data table after the migration; and if the relationship between the data before migration and the data after migration conforms to the data migration mapping rule, determining that the data before migration and the data after migration are consistent.
For example, some intelligent conference terminals, intelligent display screen carry with intelligent conference system, can realize that real-time pronunciation are reprinted, document structured storage, content sweep yard share etc. make video conference convenient and fast's function more. And a certain conference time quota can be given when the intelligent conference terminal and the intelligent display screen are sold, when the intelligent conference terminal and the intelligent display screen are used for carrying out the video conference, the given conference time quota is deducted according to the actual time of the conference, when the actual time of the video conference reaches the given conference time quota, the conference cannot be carried out, or the conference time quota needs to be purchased. Illustratively, a conference time quota given by an intelligent conference terminal during sale is 6 hours per day, when the intelligent conference terminal is used for carrying out a video conference, the conference time quota given on the current day is deducted according to the actual time of the video conference, if the actual time of the video conference reaches 6 hours on the current day, the deduction reaches an upper limit value, the conference cannot be carried out, and the conference time quota needs to be purchased, and some intelligent conference terminals do not support the service of purchasing the conference time quota, so that the conference cannot be continued when the deduction reaches the upper limit value, and the use of a user is inconvenient.
The conference time duration quotas of the devices capable of carrying out the video conference are communicated, so that the devices capable of carrying out the video conference can share the conference time duration quotas of the other sides, one device can deduct the conference time duration quotas of the other devices when carrying out the video conference, the time duration that the device can carry out the video conference is prolonged, the convenience of use of a user is improved, and the user experience is also improved.
Therefore, if the conference duration quotas of a plurality of video conference capable devices are to be opened, the same server is required to perform unified conference duration quota management on the plurality of video conference capable devices. For example, if the conference duration quota between the intelligent conference terminal and the intelligent display screen needs to be communicated, the same server needs to perform unified conference duration quota management on the intelligent conference terminal and the intelligent display screen. If the conference time quota of the intelligent conference terminal and the intelligent display screen is 6 hours per day, the total deduction amount of the server is 12 hours, and when the intelligent conference terminal and the intelligent display screen carry out the video conference, the deduction amount is carried out from 12 hours according to the current time of the video conference until the current conference time of the intelligent conference terminal and the intelligent display screen reaches 12 hours.
If the same server is used to perform unified conference time quota management on the multiple video conference-capable devices and the target device in the server does not have related data stored in the multiple video conference-capable devices, the related data of the target device needs to be migrated to the server. For example, if the server is used to perform unified conference duration quota management on the intelligent conference terminal and the intelligent display screen, and the relevant data of the intelligent display screen is stored in the server, and the relevant data of the intelligent conference terminal is not stored in the server, the relevant data of the intelligent conference terminal needs to be migrated to the server. The related data comprises deduction data of a historical conference, records of the historical conference, remaining conference duration and the like.
After the data of the intelligent conference terminal is migrated to the server, the server performs a verification process of migration consistency.
Optionally, in another embodiment of the present application, the target data includes a first type of data and a second type of data;
the server 300 determines whether the relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule, including:
and respectively judging whether the first type of data and the second type of data before and after migration both accord with respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration accords with a preset data migration mapping rule based on the judgment result.
Optionally, in another embodiment of the present application, the server 300 respectively determines whether the first type of data and the second type of data before and after migration both conform to respective corresponding data migration mapping rules, and determines whether a relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule based on a result of the determination, including:
judging whether the relation between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data;
if the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, judging whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data;
and if the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data, determining that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
Optionally, in another embodiment of the present application, the server 300 is further configured to:
if the relationship between the second type data before migration and the second type data after migration does not accord with the data migration mapping rule corresponding to the second type data, generating error prompt information of the second type data which is not migrated according to the corresponding data migration mapping rule, and determining that the relationship between the data before migration and the data after migration accords with the data migration mapping rule, or determining that the relationship between the data before migration and the data after migration does not accord with the data migration mapping rule.
Optionally, in another embodiment of the present application, the determining, by the server 300, whether the relationship between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data includes:
judging whether the relation between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration meets the data migration mapping rule corresponding to the first type of data;
and if the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data, determining that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
Optionally, in another embodiment of the present application, the determining, by the server 300, whether a relationship between a value corresponding to the first type of data before the migration and a value corresponding to the first type of data after the migration meets a data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to equal-quantity migration before migration is the same as the corresponding numerical value after migration;
if the corresponding numerical value of the first type of data subjected to the equal-amount migration before the migration is the same as the corresponding numerical value after the migration, determining that the relationship between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration accords with the data migration mapping rule corresponding to the first type of data.
Optionally, in another embodiment of the present application, the determining, by the server 300, whether a relationship between a value corresponding to the first type of data before the migration and a value corresponding to the first type of data after the migration meets a data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to unequal migration after migration is the corresponding numerical value before migration or not, and mapping the corresponding numerical value through an unequal migration mapping rule to obtain the numerical value;
if the numerical value corresponding to the first type of data subjected to unequal amount migration after migration is obtained by mapping the numerical value corresponding to the first type of data before migration through the unequal amount migration mapping rule, determining that the relationship between the numerical value corresponding to the first type of data before migration and the numerical value corresponding to the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
Optionally, in another embodiment of the present application, the server 300 is configured to:
before judging whether the total amount of the data before migration and the total amount of the data after migration are the same, determining storage position information of the target data before migration and after migration based on a preset data migration rule;
and reading the data before migration and the data after migration according to the storage position information of the target data before and after migration.
The intelligent conference system provided in this embodiment, which belongs to the same application concept as the data migration consistency verification method provided in the foregoing embodiment of the present application, may perform the data migration consistency verification method provided in any of the foregoing embodiments of the present application, have the functional modules corresponding to the data migration consistency verification method and the technical details whose beneficial effects are not described in detail in this embodiment, refer to the specific processing contents of the data migration consistency verification method provided in the foregoing embodiment of the present application, and are not described herein again.
In addition to the above-described methods and apparatus, embodiments of the present application may also be a computer program product comprising computer program instructions that, when executed by the processor 210, cause the processor 210 to perform the steps of the data migration consistency verification method provided by the above-described embodiments.
The computer program product may be used to write program code for performing the operations of embodiments of the present application in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server.
Furthermore, embodiments of the present application may also be a computer-readable storage medium having stored thereon computer program instructions, which, when executed by a processor, cause the processor 210 to perform the steps of the data migration consistency verification method provided by the above-described embodiments.
The computer readable storage medium may take any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may include, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
While, for purposes of simplicity of explanation, the foregoing method embodiments have been described as a series of acts or combination of acts, it will be appreciated by those skilled in the art that the present application is not limited by the order of acts or acts described, as some steps may occur in other orders or concurrently with other steps in accordance with the application. Further, those skilled in the art should also appreciate that the embodiments described in the specification are preferred embodiments and that the acts and modules referred to are not necessarily required in this application.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and reference may be made to the partial description of the method embodiment for relevant points.
The steps in the method of each embodiment of the present application may be sequentially adjusted, combined, and deleted according to actual needs, and technical features described in each embodiment may be replaced or combined.
The modules and sub-modules in the device and the terminal in the embodiments of the application can be combined, divided and deleted according to actual needs.
In the several embodiments provided in the present application, it should be understood that the disclosed terminal, apparatus and method may be implemented in other manners. For example, the above-described terminal embodiments are merely illustrative, and for example, the division of a module or a sub-module is only one logical function division, and other division manners may be available in actual implementation, for example, a plurality of sub-modules or modules may be combined or integrated into another module, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or modules, and may be in an electrical, mechanical or other form.
The modules or sub-modules described as separate parts may or may not be physically separate, and parts that are modules or sub-modules may or may not be physical modules or sub-modules, may be located in one place, or may be distributed over a plurality of network modules or sub-modules. Some or all of the modules or sub-modules can be selected according to actual needs to achieve the purpose of the solution of the present embodiment.
In addition, each functional module or sub-module in the embodiments of the present application may be integrated into one processing module, or each module or sub-module may exist alone physically, or two or more modules or sub-modules may be integrated into one module. The integrated modules or sub-modules can be implemented in the form of hardware, and can also be implemented in the form of software functional modules or sub-modules.
Those of skill would further appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied directly in hardware, in a software unit executed by a processor, or in a combination of the two. The software cells may be located in Random Access Memory (RAM), memory, read Only Memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art.
Finally, it should also be noted that, in this document, relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrases "comprising one of 8230; \8230;" 8230; "does not exclude the presence of additional like elements in a process, method, article, or apparatus that comprises the element.
The previous description of the disclosed embodiments is provided to enable any person skilled in the art to make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (12)

1. A data migration consistency verification method is characterized by comprising the following steps:
judging whether the total data amount of the target data before migration is the same as the total data amount after migration;
if the total amount of the data before the migration is the same as the total amount of the data after the migration, judging whether the relation between the data before the migration and the data after the migration accords with a preset data migration mapping rule or not; the data migration mapping rule comprises a mapping relation between fields in the data table before migration and fields in the data table after migration;
and if the relationship between the data before the migration and the data after the migration conforms to the data migration mapping rule, determining that the data before the migration and the data after the migration are consistent.
2. The method of claim 1, wherein the target data comprises a first class of data and a second class of data;
the judging whether the relationship between the data before the migration and the data after the migration meets the preset data migration mapping rule or not includes:
and respectively judging whether the first type of data and the second type of data before and after migration both accord with respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration accords with a preset data migration mapping rule based on the judgment result.
3. The method according to claim 2, wherein the respectively determining whether the first type of data and the second type of data before and after migration both conform to respective corresponding data migration mapping rules, and determining whether the relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule based on the determination result comprises:
judging whether the relation between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data;
if the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data, judging whether the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data;
and if the relationship between the second type of data before migration and the second type of data after migration conforms to the data migration mapping rule corresponding to the second type of data, determining that the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
4. The method of claim 3, further comprising:
if the relationship between the second type data before migration and the second type data after migration does not accord with the data migration mapping rule corresponding to the second type data, generating error prompt information of the second type data which is not migrated according to the corresponding data migration mapping rule, and determining that the relationship between the data before migration and the data after migration accords with the data migration mapping rule, or determining that the relationship between the data before migration and the data after migration does not accord with the data migration mapping rule.
5. The method according to claim 3, wherein the determining whether the relationship between the first type of data before migration and the first type of data after migration meets a data migration mapping rule corresponding to the first type of data includes:
judging whether the relation between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration meets the data migration mapping rule corresponding to the first type of data or not;
and if the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data, determining that the relationship between the first type of data before migration and the first type of data after migration conforms to the data migration mapping rule corresponding to the first type of data.
6. The method according to claim 5, wherein if the data migration mapping rule is an equivalent migration mapping rule, the determining whether a relationship between a corresponding numerical value of the first type of data before the migration and a corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to equal-quantity migration before migration is the same as the corresponding numerical value after migration;
if the corresponding numerical value of the first type of data subjected to the equal-amount migration before the migration is the same as the corresponding numerical value after the migration, determining that the relationship between the corresponding numerical value of the first type of data before the migration and the corresponding numerical value after the migration accords with the data migration mapping rule corresponding to the first type of data.
7. The method according to claim 5, wherein if the data migration mapping rule is an unequal migration mapping rule, the determining whether a relationship between a corresponding numerical value of the first type of data before the migration and a corresponding numerical value after the migration conforms to the data migration mapping rule corresponding to the first type of data includes:
judging whether the corresponding numerical value of the first type of data subjected to unequal migration after migration is the corresponding numerical value before migration or not, and mapping the corresponding numerical value through the unequal migration mapping rule to obtain the numerical value;
and if the corresponding numerical value of the first type of data subjected to unequal migration after migration is obtained by mapping the corresponding numerical value before migration through the unequal migration mapping rule, determining that the relationship between the corresponding numerical value of the first type of data before migration and the corresponding numerical value after migration conforms to the data migration mapping rule corresponding to the first type of data.
8. The method according to claim 1, wherein before determining whether the total amount of data before migration and the total amount of data after migration are the same, further comprising:
determining storage position information of target data before and after migration based on a preset data migration rule;
and reading the data before the migration and the data after the migration according to the storage position information of the target data before the migration and after the migration.
9. A data migration consistency verification apparatus, comprising:
the first judgment module is used for judging whether the total data amount of the target data before migration is the same as the total data amount after migration;
the second judgment module is used for judging whether the relationship between the data before migration and the data after migration conforms to a preset data migration mapping rule or not if the total amount of the data before migration is the same as the total amount of the data after migration; the data migration mapping rule comprises a mapping relation between fields in the data table before migration and fields in the data table after migration;
and the determining module is used for determining that the data before migration and the data after migration are consistent if the relationship between the data before migration and the data after migration conforms to the data migration mapping rule.
10. An intelligent conferencing system, comprising:
the intelligent conference system comprises a server, an intelligent conference terminal and an intelligent display screen, wherein the intelligent conference terminal and the intelligent display screen are respectively connected with the server;
the server is used for storing data for supporting the intelligent conference terminal and the intelligent display screen to share the conference use duration;
when the intelligent conference terminal and/or the intelligent display screen migrate data to the server, the server judges whether the total data amount of the target data before migration is the same as the total data amount after migration; if the total amount of the data before migration is the same as the total amount of the data after migration, judging whether the relationship between the data before migration and the data after migration meets a preset data migration mapping rule or not, wherein the data migration mapping rule comprises the mapping relationship between fields in a data table before migration and fields in a data table after migration; and if the relationship between the data before the migration and the data after the migration conforms to the data migration mapping rule, determining that the data before the migration and the data after the migration are consistent.
11. An electronic device, comprising:
a memory and a processor;
wherein the memory is used for storing programs;
the processor is configured to implement the data migration consistency verification method according to any one of claims 1 to 8 by executing the program in the memory.
12. A storage medium, comprising: the storage medium has a computer program stored thereon, and when the computer program is executed by a processor, the computer program realizes the steps of the data migration consistency verification method according to any one of claims 1 to 8.
CN202210851510.4A 2022-07-19 2022-07-19 Data migration consistency verification method, device, system, equipment and storage medium Pending CN115292277A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210851510.4A CN115292277A (en) 2022-07-19 2022-07-19 Data migration consistency verification method, device, system, equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210851510.4A CN115292277A (en) 2022-07-19 2022-07-19 Data migration consistency verification method, device, system, equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115292277A true CN115292277A (en) 2022-11-04

Family

ID=83823496

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210851510.4A Pending CN115292277A (en) 2022-07-19 2022-07-19 Data migration consistency verification method, device, system, equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115292277A (en)

Similar Documents

Publication Publication Date Title
US11216476B2 (en) Data processing method, apparatus, and device
CN110162662B (en) Verification method, device and equipment for data records in block chain type account book
CN111259643B (en) Method and equipment for generating graphic report
US20140222766A1 (en) System and method for database migration and validation
CN107451112B (en) Form tool data checking method, device, terminal equipment and storage medium
WO2021239074A1 (en) Smart contract code generation method, program, and device
CN107391357A (en) Application crashes replay method, device and mobile terminal
US20210124752A1 (en) System for Data Collection, Aggregation, Storage, Verification and Analytics with User Interface
CN114092252A (en) Block chain transaction execution method, device, equipment and readable storage medium
CN111177113A (en) Data migration method and device, computer equipment and storage medium
CN110198327B (en) Data transmission method and related equipment
CN110688145A (en) Android MVP code automatic generation method, device, medium and electronic equipment
CN110168589B (en) Methods and apparatus for tracking, capturing, and synchronizing activity data across multiple devices
WO2022156087A1 (en) Data blood relationship establishing method and apparatus, computer device, and storage medium
CN109614271A (en) Control method, device, equipment and the storage medium of multiple company-data consistency
CN112579891A (en) Cloud resource recommendation method and device, electronic terminal and storage medium
CN113742338A (en) Structured storage system for project acceptance forms
WO2021013057A1 (en) Data management method and apparatus, and device and computer-readable storage medium
CN111367982A (en) Method and device for importing TRIRIGA basic data, computer equipment and storage medium
CN105988986A (en) Information processing method and device
US7636902B1 (en) Report validation tool
CN110362294A (en) Development task executes method, apparatus, electronic equipment and storage medium
CN113626438B (en) Data table management method, device, computer equipment and storage medium
CN115292277A (en) Data migration consistency verification method, device, system, equipment and storage medium
CN110244934B (en) Method and device for generating product demand document and test information

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