File content verification method, system and device, storage medium and program product
By monitoring file changes in real time and using the verification rule module for rule analysis and verification, data verification problems in different file systems and file types are solved, and accurate checksum automation management at the field level is realized.
Patent Information
- Application Number
- CN202411524128.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-29
- Publication Date
- 2025-03-07
AI Technical Summary
The prior art is difficult to effectively verify file data of different file systems and file types, especially in large data volumes and multi-rule scenarios, making it difficult to ensure data accuracy.
The file monitoring system is monitored in real time for file changes, and the verification rule is used to match and parse the verification rules, and the rule checking is carried out in combination with the data engine and the computing engine module to realize field-level verification of different file systems and file types.
Realize field-level verification of different file systems and file types to ensure data accuracy, and reduce the complexity and management difficulty of manual verification through real-time monitoring and automated verification.
Smart Images
Figure CN119576866A_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of data processing technology, and in particular to a file content verification method, system, device, storage medium and program product. Background Art
[0002] In daily document disclosure, it is necessary to ensure the accuracy of domestic freight rate operation and maintenance data. Sometimes, due to the large amount of data in the file, it is difficult to ensure data accuracy only by manual verification. For Excel files, basic data accuracy can be guaranteed by building some simple cross-references, but other types of files such as txt, xml, json, etc. cannot be guaranteed.
[0003] In addition, some domestic freight rate configuration files have extremely high requirements. Manual verification sometimes cannot meet the verification needs, or problems cannot be discovered in time. At this time, a set of automated verification rules is needed to ensure the accuracy of the data.
[0004] At the same time, when performing manual verification, management difficulties will arise when there are too many verification rules, and various rules will be scattered everywhere, making it inconvenient to manage, view, and optimize. For example, there is an Excel file with 1,000 cells for domestic freight rates, of which 100 cells need to be verified, then 100 corresponding verification rules will be generated. If there are 1,000 files that need to be verified, the number of rules generated will increase exponentially, and the management and classification of these rules is still a big problem.
[0005] Therefore, there is an urgent need for a file data content verification method that can be used for different file systems and file types to achieve field-level verification. Summary of the invention
[0006] The present invention aims to provide a file content verification method, system, device, storage medium and program product to implement file field level verification of different file systems and different file types.
[0007] To achieve the above object, the present invention provides the following technical solutions:
[0008] In a first aspect, an embodiment of the present invention provides a file content verification method, comprising:
[0009] When the file monitoring system monitors the changed files, it publishes the change message of the changed files;
[0010] Obtain the change information of the changed file through the verification rule module, and match the corresponding file verification rule according to the change information of the changed file;
[0011] Use the rule parsing module to perform syntax parsing on the verification rules of the changed file to obtain the parsing result;
[0012] The data engine module reads the changed file according to the analysis result, and sends the changed file data to the calculation engine module for rule checking calculation to obtain the checking result, thereby realizing content verification of the changed file.
[0013] In a second aspect, an embodiment of the present invention provides a file content verification system, including:
[0014] The file monitoring system is used to monitor files and publish change messages of the changed files when a changed file is detected.
[0015] The verification rule module is used to obtain the change message of the changed file and match the corresponding file verification rule according to the change message of the changed file;
[0016] A rule parsing module is used to parse the check rules of the changed file and obtain the parsing result;
[0017] A data engine module, used for reading the change file according to the analysis result, and sending the change file data to the calculation engine module;
[0018] The calculation engine module is used to perform rule verification calculations on the changed file data to obtain verification results and realize content verification of the changed file.
[0019] In a third aspect, an embodiment of the present invention further provides an electronic device, including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program or instructions to implement the aforementioned file content verification method.
[0020] In a fourth aspect, an embodiment of the present invention further provides a computer storage medium, wherein a computer program or instruction is stored in the computer storage medium, and the computer program or instruction implements the aforementioned file content verification method when executed by a processor.
[0021] In a fifth aspect, an embodiment of the present invention further provides a computer program product, including a computer program or instructions, which implement the aforementioned file content verification method when executed by a processor.
[0022] The technical effects and advantages of the present invention are as follows: 1. The present invention can ensure the accuracy of field-level data verification through flexible field reading and custom function verification for different file systems and file types; through JOIN connection in the SQL-like language, it can realize the verification of cross-data source fields of two files or even multiple files; through different file READERs and functions, it can realize field verification of file types such as xml, json, etc., and at the same time, it provides corresponding extension points to realize the verification of other types of files such as CSV files, etc.;
[0023] 2. The present invention monitors the target file system in real time. When files in the target file system are added, deleted, or modified, the corresponding message will be published. After the verification rule module receives the subscription message by subscribing to the corresponding message middleware, it will trigger the file content verification system to check the file content. When the verification is inconsistent, the system will promptly notify the relevant personnel, thereby ensuring that the impact on the target file system is minimized.
[0024] 3. The present invention provides factual basis for the improvement of the file content verification system through systematic management and daily operation and maintenance with built-in rules; through personalized output display of file verification results and different template engine modules, the verification results can be displayed to relevant personnel according to personalized needs.
[0025] Other features and advantages of the present invention will be described in the following description, and partly become apparent from the description, or understood by practicing the present invention. The purpose and other advantages of the present invention can be realized and obtained by the structures pointed out in the description, claims and drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0026] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0027] Figure 1 A flowchart of a file content verification method according to an embodiment of the present invention;
[0028] Figure 2 Detailed flow chart of the file content verification method according to an embodiment of the present invention;
[0029] Figure 3 This is a display effect diagram of the file verification result in an embodiment of the present invention;
[0030] Figure 4 A schematic diagram of the overall architecture of a file content verification system according to an embodiment of the present invention;
[0031] Figure 5 The figure is a schematic diagram of the structure of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0032] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0033] To address the deficiencies of the prior art, the present invention discloses a method for verifying file contents. Figure 1 As shown, the following steps are included:
[0034] Step S1: When the file monitoring system monitors a changed file, it publishes a change message of the changed file;
[0035] Step S2: obtaining the change message of the changed file through the verification rule module, and matching the corresponding file verification rule according to the change message of the changed file;
[0036] Step S3: using the rule parsing module to perform syntax parsing on the check rules of the changed file to obtain the parsing result;
[0037] Step S4: the data engine module reads the changed file according to the analysis result, and sends the changed file data to the calculation engine module for rule checking calculation to obtain the checking result, thereby realizing content verification of the changed file.
[0038] In some specific embodiments, step S1: when the file monitoring system monitors a changed file, it publishes a change message of the changed file; Figure 3 As shown, including the following:
[0039] The file monitoring module is used to sense or monitor the changes or modifications of files in the directory of the target file system (such as the domestic freight rate file system); the file changes include: adding, modifying and deleting files, etc. The target file system includes OSS cloud disk, FTP server and local disk, etc.
[0040] The file monitoring module monitors the target file system mainly in the following two ways:
[0041] (1) Register the listener corresponding to the target file system. When the files in the target file system directory are changed, the listener corresponding to the target file system will be triggered;
[0042] (2) Setting a scheduled scanning task for the target file: When the target file system does not support listener registration, the target file system can be scanned regularly through a scheduled scanning task to achieve monitoring of the target file system; when a file on the target file system directory changes, a message will be triggered.
[0043] When the target file system changes, the upstream module needs to be informed. That is to say, if a file changes, the file content needs to be verified for the changed file (i.e., the changed file). Therefore, the file monitoring module publishes the change message corresponding to the changed file through the message middleware (MQ) to inform the upstream module.
[0044] The change message corresponding to the changed file includes: the change type of the changed file (i.e., addition / modification / deletion of a file), the target file system type where the changed file is stored (i.e., OSS / FTP / local disk file), the address (URI) where the changed file is stored, and the name of the changed file;
[0045] Among them, a changed file can be uniquely locked through the storage address and name of the file; the underlying storage of the file is a disk (local disk or cloud disk), and the target file system manages the files on the disk.
[0046] Step S2: Obtain the change message of the change file through the verification rule module, and match the corresponding file verification rule according to the change message of the change file; Figure 2 As shown, including the following:
[0047] Before checking the contents of files, the checking rules for different files are defined using the checking rule module.
[0048] Among them, verification rules refer to: a series of rules and standards that need to be followed when verifying file data;
[0049] The content of the file verification rules includes: the name of the verification rule, the type of verification rule, the F-CEL language expression, the configuration of the changed file, the verification result rendering module, and the status of the verification rule; among which, the F-CEL language expression is the specific verification rule of the file.
[0050] The verification rule module subscribes to the corresponding message middleware, and after receiving the subscribed message, that is, after receiving the change message of the change file, the verification rule module is started;
[0051] The verification rule module queries all the verification rule contents of the changed file according to the name, storage system and storage path of the changed file in the change message, and loads the rule configuration file of the changed file according to the specific verification rules.
[0052] The rule configuration file of the change file defines the reading rules of the change file; for example:
[0053] Defines whether to skip the first line when reading the corresponding file type (Excel, txt, json, xml, etc.) (some first lines are just some descriptive descriptions and do not need to be checked);
[0054] Define the corresponding file encoding format (UTF-8, GBK) and read it in this encoding format when reading the file to prevent garbled characters from being generated in the read file.
[0055] In the verification rule module, one verification rule corresponds to multiple verification instances; for example, when a file changes, a verification rule of a certain file will generate a corresponding verification instance, which records the verification process, such as the result of this verification.
[0056] Step S3: Use the rule parsing module to perform syntax parsing on the check rules of the changed file to obtain the parsing result; Figure 2 As shown, including the following:
[0057] The checking rules for each file are defined by F-CEL language expressions; wherein F-CEL language is an SQL-like expression language;
[0058] F-CEL language expressions include: SELECT clause, FROM clause, WHERE clause, JOIN clause, GROUP clause, ORDER clause, LIMIT clause and other parts, basically including all the elements of SQL language.
[0059] Therefore, the rule parsing module mainly processes the verification rules of the change file defined in the F-CEL language through the antlr framework or regular expressions, that is, it performs syntax parsing on the SQL-like language and obtains the parsing result as corresponding multiple SQL-like clauses; then the rule parsing module obtains the file type of the change file according to the parsing result, and routes the data of the change file to the corresponding data engine module for processing according to the file type.
[0060] Among them, each SQL-like clause corresponds to a processing logic of the verification rule module, for example: the SELECT clause corresponds to the data reading logic of the verification rule module, the WHERE clause corresponds to the calculation logic of the verification rule module, the JOIN clause corresponds to the cross-file processing logic of the verification rule module, the GROUP clause corresponds to the grouping calculation logic of the verification rule module, and the ORDER clause corresponds to the sorting logic of the verification rule module; when the F-CEL language parsing is completed, the corresponding SQL-like clause will be given to the corresponding processing logic of the verification rule module (that is, the corresponding data engine module) for processing.
[0061] An example of the syntax of the F-CEL language is shown below:
[0062] SELECT row(cell(1))as c1,row(cell(2))as c2,row(cell(3))as c3 FROMFTPReader('url','test.xlsx')WHERE c1+c2! =c3;
[0063] This language script means reading the first, second and third columns of all rows in the test.xlsx file from the domestic freight rate FTP server. If the sum of the first and second columns is not equal to the third column, the verification fails. This sample language is used to simulate the verification of the cross-reference relationship of an Excel file.
[0064] For example, the meanings of each SQL-like clause obtained by parsing the rule parsing module include:
[0065] (1) The SELECT clause defines the row and column information of the file to be checked (i.e., the changed file) that needs to be scanned; the row and column information is implemented through custom keywords, such as row() is used to read the rows of Excel files, and cell() is used to read the columns of Excel files; for example, xpath() is used to read the data of xml files, and jpath() is used to read the data of json files;
[0066] (2) The FROM clause defines which file READER is used to read the changed file; for example, OSSReader is a file processor that reads files on OSS, FTPReader is a file processor that reads files on FTP servers, and FileReader is a file processor that reads files on local disks.
[0067] (3) The WHERE clause defines the specific verification rules for the change file; for example, it determines whether 1+1=2 is correct, whether 2023-08-23 is a date format, etc. The specific calculation is performed by the calculation engine module;
[0068] (4) The JOIN clause is defined to check data across files. For example, if you need to determine whether field1 in table 1 is equal to field2 in table 2, the syntax example is as follows:
[0069] SELECT row(cell(1))as c1,row(cell(2))as c2,row(cell(3))as c3FROMFTPReader('uri','test.xlsx')as t1 where c1! =null LEFT JOIN(SELECT jpath('$info.name')as name FROM OSSReader('uri','jsontest.json')as t2 where name!=null)on t1.c1! =t2.name;
[0070] This language script defines the verification rules for two files, namely file 1: test.xlsx, file 2: jsontest.json; among them, file 1 reads the first column, the second column, and the third column, and file 2 reads the value of the name field under the info node. When column 1 of file 1 is not equal to the name value of file 2, the verification fails. If you need to verify three files, you only need to add the corresponding JOIN clause. The final parsing result of this language script is as follows:
[0071]
[0072]
[0073] Among them, Reader is the coordinate of the file, which can uniquely locate the position of the file to be checked.
[0074] Step S4: the data engine module reads the changed file according to the analysis result, and sends the changed file data to the calculation engine module for rule checking calculation to obtain the checking result, so as to verify the content of the changed file; Figure 2 The specific contents are as follows:
[0075] Step S41: The data engine module is mainly used to process file data. After the rule parsing module routes the data of the changed file to the corresponding data engine module, the data engine module reads the data of the changed file according to the parsing result and transmits it to the corresponding computing engine module through the data pipeline.
[0076] For example, if the changed file is a file on the domestic freight rate file system directory, and the target file system type (i.e., the domestic freight rate file system) where the changed file is stored is OSS, then the rule parsing module routes the data of the changed file to the OSSReader processor, which integrates various read operations on the OSS file system, and the read data will be transmitted to the domestic freight rate calculation engine module through the data pipeline.
[0077] Among them, the data pipeline is a channel for data flow. Since the file to be verified (i.e., the changed file) may be very large, the verification of this file cannot read the file into the memory at one time and then perform file content verification; therefore, the present invention adopts the data flow to flow into the computing engine module in a pipeline manner for computing operations, thereby avoiding the problem of excessive memory consumption.
[0078] An example of data stream transmission in pipeline mode: the data engine module reads 100 lines of the change file each time, and after reading, it packages them and sends them to the calculation engine module for calculation.
[0079] Step S42: After the data engine module transmits the data of the change file to the calculation engine module in a pipeline manner, the calculation engine module calculates the parsing result (ie, each SQL-like clause), obtains the verification result of the change file and stores it in the cloud.
[0080] The calculation engine module first calculates the conditions of each WHERE clause, and then calculates the expression of the ON clause. The calculation framework can be Apache Commons JEXL, which supports the calculation of various expressions.
[0081] The computing modes of the computing engine module include a fast failure mode and a full computing mode;
[0082] The fast failure mode means that as long as the calculation engine module has a calculation verification exception, the calculation will be stopped and then fed back to the data engine module. After receiving the feedback, the data engine module will stop reading the data of the changed file and stop the data flow transmission to the calculation engine module;
[0083] The full calculation mode is that the entire file content verification process is not truly completed until all data calculations and verifications of the changed file are completed.
[0084] After the calculation engine module performs a series of calculations on each SQL clause, it obtains the verification results of the changed files. The verification results may be very large and will be stored on OSS. If you are not particularly concerned about the verification results, you can only store a limited number of items (for example, 5 items) and then only prompt the total number of verification results (for example, 2000). This can be stored in the database. The final effect is similar to the attached Figure 3 .
[0085] Step S43: Display the verification result of the changed file through the template engine module, which specifically includes the following contents:
[0086] First, according to different display requirements, different template engine modules are selected to display the verification results of the changed files; such as MarkDown, FreeMark, Velocity, etc.
[0087] Since the verification rule module has defined the verification result rendering templates for different files (i.e., the rendering templates in different template engine modules) in the above step S2, after selecting the template engine module corresponding to the changed file, the template engine module is used to load the rendering template file corresponding to the changed file according to the configuration data of the verification result rendering template.
[0088] The template engine module renders the loaded rendering template file. After the rendering is successful, the verification result of the changed file can be displayed; for example, the result can be displayed through a web page or a robot. The final effect is shown in the attached Figure 3 .
[0089] Among them, the rendering of the rendering template file has two elements: one is the rendered template file, and the other is the calculation engine result; therefore, the rendering process of the rendering template file is: replace the variables in the rendering template file with the verification result of the change file, for example:
[0090] #foreach($itemin$detailIterator)
[0091] $! {item.tradeMode},$! {item.direction},$! {item.name}
[0092] #end
[0093] The above example is a rendering template for the Velocity template engine module.
[0094] That is, the present invention displays the verification result on the client through the rendering template engine mode and the rendering template file defined in the verification rule.
[0095] In the process of checking the file content, the present invention also utilizes a checking rule operation and maintenance module, which is mainly an operation and maintenance management platform for managing the rule management of the verification rule module in the target file system (e.g., the domestic freight rate file system), including the configuration or definition, modification, deletion, online and offline of the checking rules, and statistics of the checking results of some checking rules, etc. That is, the checking rule operation and maintenance module mainly performs classification management of the checking rules.
[0096] The present invention can ensure the accuracy of field-level data verification through flexible field reading and custom function verification, such as whether a field in an Excel table is of date type; through the JOIN connection of the SQL-like language, it can realize the verification of cross-data source fields of two files or even multiple files, such as whether the cross-reference relationships in two Excel tables are consistent.
[0097] The present invention can implement field verification of file types such as xml and json through different file READERS and functions, for example, whether a field of an xml file is in digital format; and provides corresponding extension points to implement verification of other types of files, such as CSV files.
[0098] The present invention realizes the field-level verification of a single file / multiple files of domestic freight rates in a SQL-like language manner, and the F-CEL language has good comprehensibility, and can be easily mastered as long as one has a certain understanding of SQL; when a domestic freight rate file is changed, the verification status after the file change can be perceived in quasi-real time, and the risks caused by the file change can be perceived in time, making the risks controllable.
[0099] The present invention is equipped with a corresponding rule management and operation and maintenance platform (i.e., file content verification system), which can classify and manage a large number of verification rules and visualize file risks; it supports verification of various types of files, while retaining corresponding extension points (implementing Reader interface) to facilitate later expansion and optimization of the system.
[0100] Based on the same inventive concept, the embodiment of the present invention also provides a file content verification system, such as Figure 4 As shown, the system comprises:
[0101] The file monitoring system is used to monitor files and publish change messages of the changed files when a changed file is detected.
[0102] The verification rule module is used to obtain the change message of the changed file and match the corresponding file verification rule according to the change message of the changed file;
[0103] A rule parsing module is used to parse the check rules of the changed file and obtain the parsing result;
[0104] A data engine module, used for reading the change file according to the analysis result, and sending the change file data to the calculation engine module;
[0105] The calculation engine module is used to perform rule verification calculations on the changed file data to obtain verification results and realize content verification of the changed file.
[0106] The system further comprises: a template engine module for displaying the verification result of the changed file;
[0107] The template engine module is specifically used to render the template according to the verification result defined by the verification rule module, load the rendering template file corresponding to the changed file; render the loaded rendering template file to display the verification result of the changed file.
[0108] The system also includes: a verification rule operation and maintenance module for classifying and managing the verification rules;
[0109] The verification rule operation and maintenance module is specifically used to manage the rules of the verification rule module in the target file system, including the configuration or definition, modification, deletion, online and offline of the verification rules, and the statistics of the verification results of some verification rules.
[0110] Regarding the system in the above embodiment, the specific manner in which each unit module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0111] Based on the same inventive concept, an embodiment of the present invention further provides an electronic device, whose structure is as follows: Figure 5 As shown, it includes a memory, a processor and a computer program stored in the memory, and the processor executes the computer program or instructions to implement the aforementioned file content verification method.
[0112] Based on the same inventive concept, an embodiment of the present invention further provides a computer storage medium, in which a computer program or instruction is stored. When the computer program or instruction is executed by a processor, the aforementioned file content verification method is implemented.
[0113] Based on the same inventive concept, an embodiment of the present invention further provides a computer program product, including a computer program or instructions, which implement the aforementioned file content verification method when executed by a processor.
[0114] Finally, it should be noted that the above is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the aforementioned embodiments, it is still possible for those skilled in the art to modify the technical solutions described in the aforementioned embodiments or to make equivalent substitutions for some of the technical features therein. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.
Claims
1. A file content verification method, characterized in that: include: When the file monitoring system monitors the changed files, it publishes the change message of the changed files; Obtain the change information of the changed file through the verification rule module, and match the corresponding file verification rule according to the change information of the changed file; Use the rule parsing module to perform syntax parsing on the verification rules of the changed file to obtain the parsing result; The data engine module reads the changed file according to the analysis result, and sends the changed file data to the calculation engine module for rule checking calculation to obtain the checking result, thereby realizing content verification of the changed file.
2. The file content verification method according to claim 1, characterized in that: When the file monitoring system monitors a changed file, it publishes a change message of the changed file, including: The target file system is monitored by a file monitoring module. When a file on the target file system is changed, the file monitoring module publishes a change message corresponding to the changed file through the message middleware. Wherein, the target file system includes OSS, FTP and local disk; The change message includes: the change type of the changed file, the target file system type where the changed file is stored, the address where the changed file is stored, and the name of the changed file.
3. The file content verification method according to claim 1, characterized in that: The change message of the changed file is obtained through the verification rule module, and the corresponding file verification rules are matched according to the change message of the changed file, including: Defining the verification rule contents of different files in advance by using the verification rule module; The verification rule module receives the change message of the changed file by subscribing to the corresponding message middleware; The verification rule module matches the verification rule content of the change file according to the change message of the change file, and loads the rule configuration file of the change file; The content of the file checking rule includes: the name of the checking rule, the type of the checking rule, the F-CEL language expression, the configuration of the changed file, the checking result rendering module, and the status of the checking rule; wherein the F-CEL language expression is the checking rule of the changed file; The rule configuration file of the change file defines the reading rules of the change file.
4. The file content verification method according to claim 1, characterized in that: The rule parsing module is used to perform syntax parsing on the verification rules of the changed file to obtain parsing results, including: The checking rules for each file are defined by F-CEL language expressions; F-CEL language is an SQL-like expression language; The rule parsing module performs syntax parsing on the F-CEL language checking rules of the change file through the antlr framework to obtain the parsing result, that is, to obtain the corresponding multiple SQL-like clauses; The rule parsing module obtains the type of the changed file according to the parsing result, and routes the changed file data to the corresponding data engine module for processing according to the type of the changed file.
5. The file content verification method according to claim 1, characterized in that: The data engine module reads the change file according to the analysis result, and sends the change file data to the calculation engine module for rule checking calculation to obtain the checking result, including: The data engine module reads the data of the changed file according to the analysis result, and transmits it to the corresponding calculation engine module through the data pipeline; The calculation engine module calculates each SQL-like clause of the change file, obtains and stores the verification result of the change file; Wherein, the data pipeline adopts the pipeline mode; The computing modes of the computing engine module include a fast failure mode and a full computing mode.
6. The file content verification method according to claim 1, characterized in that: The template engine module is used to display the verification results of the changed files, including: The template engine module renders the template according to the verification result defined by the verification rule module, and loads the rendering template file corresponding to the changed file; The template engine module renders the loaded rendering template file to display the verification result of the changed file; The template engine module renders the loaded rendering template file, including: replacing the variables in the rendering template file with the verification result of the changed file.
7. A file content verification system, characterized in that: The system comprises: The file monitoring system is used to monitor files and publish change messages of the changed files when a changed file is detected. The verification rule module is used to obtain the change message of the changed file and match the corresponding file verification rule according to the change message of the changed file; A rule parsing module is used to parse the check rules of the changed file and obtain the parsing result; A data engine module, used for reading the change file according to the analysis result, and sending the change file data to the calculation engine module; The calculation engine module is used to perform rule verification calculations on the changed file data to obtain verification results and realize content verification of the changed file.
8. The file content verification system according to claim 7, characterized in that: The system further comprises: The template engine module is used to display the verification results of the changed files; The template engine module is specifically used to render the template according to the verification result defined by the verification rule module, load the rendering template file corresponding to the changed file; render the loaded rendering template file to display the verification result of the changed file.
9. An electronic device, characterized in that: It comprises a memory, a processor and a computer program stored in the memory, and the processor executes the computer program or instructions to implement the file content verification method described in any one of claims 1-6.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instruction, and when the computer program or instruction is executed by the processor, the file content verification method described in any one of claims 1-6 is implemented.
11. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the file content verification method described in any one of claims 1-6 is implemented.