CN104679782A - File version control system and method - Google Patents

Abstract

The invention provides a file version control method. The method comprises the steps of creating a base file which comprises a folder and a file in the folder; operating the base file; creating a version file after a user operates the base file. The invention further provides a file version control system. With the adoption of the method, the versions can be associated, so that the circumference of redundant data can be avoided.

Description

File version control system and method

technical field

The present invention relates to a virtual machine control system and method, in particular to a file version control system and method.

Background technique

Cloud storage service provides users with a mechanism to access files on the Web at any time. After the user uploads the file to the cloud storage space, the cloud storage system will generate a URL for the file, and through the URL, the user can download or retrieve the content of the file anytime and anywhere. In addition, some manufacturers will also provide additional value-added services, such as: encryption, access permissions, large data modification or version control, etc., so that users have greater flexibility in operating files.

Among the functions of cloud storage services, version control provides users with a backup mechanism that is different from the past. Under the same file, every modification action to the file is regarded as a new version, for example, the modification time separates the versions. As shown in Figure 1, the version control architecture is based on a tree structure, the root node is the file name, and the child nodes are versions, which are distinguished by modification time. Users can download specific versions to achieve file protection mechanism.

Although the version control function in the cloud storage service provides a very convenient file protection mechanism, it can only perform version control for the modification of a single file. If the user wants to perform version control on the entire folder, it may not be possible under the current architecture. For example, if a user wants to execute the cloud storage service of MadReduce, both the input and output data are stored in the cloud storage space, and are distinguished by folders, as shown in Figure 2. When the user wants to update the input data, but wants to keep the original file Folder Input_folder, it is necessary to re-upload the files in the entire folder Input_folder. If the user only wants to update the input_file1 data under the folder Input_folder, in order to maintain the current version, the entire folder can only be re-uploaded under the current architecture, thus causing redundancy of the files input_file2 and input_file3.

Contents of the invention

In view of the above, it is necessary to provide a file version control system, which can associate versions with each other, so as to avoid redundant data.

In view of the above, it is also necessary to provide a file version control method, which can associate versions with each other, so as to avoid redundant data.

A file version control system, the system runs in a data center, the system includes: a creation module, used to create a basic file, the basic file is composed of a folder and the files under the folder; an operation module, used to The base file is operated; the creation module is also used to create a version file when the user completes the base file operation. The version file is generated by the base file operation and has a sequence relationship and a recursive structure. For each The operation of the version file will generate the next version file. For the next version file, the previous version file is the base file, and the duplicated parts of the version file and the base file are saved in the form of pointers.

A file version control method, the method includes: creating a basic file, the basic file is composed of a folder and the files under the folder; operating the basic file; when the user completes the basic file operation, the version file Create, the version file is generated by the operation of the basic file, has a sequential relationship and a recursive structure, and the operation of each version file will generate the next version file, and the previous version file is the basic file for the next version file. Among them, the duplicated parts in the version file and the basic file are saved in the form of pointers.

Compared with the prior art, the file version control system and method provided by the present invention can associate versions with each other, thereby avoiding redundant data.

Description of drawings

Fig. 1 is a schematic diagram of a file in the prior art.

Fig. 2 is a schematic diagram of folders in the prior art.

Fig. 3 is an application environment diagram of a preferred embodiment of the file version control system of the present invention.

Fig. 4 is a schematic structural diagram of a preferred embodiment of the data center of the present invention.

Fig. 5 is a flowchart of a preferred embodiment of the file version control method of the present invention.

Fig. 6 is a schematic diagram of the relationship between the basic file and the version file in the present invention.

Fig. 7 is a schematic diagram of the recursive process of the basic file and the version file in the present invention.

Fig. 8 is a schematic diagram of the structure of the basic file of the present invention.

Fig. 9 is a schematic diagram of the modified basic file of the present invention.

Fig. 10 is a schematic diagram of the structure of the new basic file in the present invention.

Fig. 11 is a schematic structural diagram of another new basic file of the present invention.

Fig. 12 is a schematic diagram of the structure of deleting basic files in the present invention.

Fig. 13 is a schematic diagram of the operation interface of the version control of the present invention.

Fig. 14 is a schematic diagram of the user operating on the version control interface of the present invention.

Description of main component symbols

client 20 database 30 network 40 data center 50 file version control system 500 create module 510 Operation module 520

The following specific embodiments will further illustrate the present invention in conjunction with the above-mentioned drawings.

Detailed ways

Referring to FIG. 3 , it is an application environment diagram of a preferred embodiment of the file version control system 500 of the present invention. The file version control system 500 is applied in the data center 50 . The data center 50 is a computer cluster composed of multiple servers. The data center 50 is used to provide cloud storage and cloud computing functions, and to perform version control on files.

The client 20 communicates with the data center (Data Center) 50 through the network 40. The client 20 is used to provide an interactive interface to the user, so that the user can log in to the data center 50 and operate the data center 50 . The client 20 may be a personal computer, a notebook computer, a mobile phone, a tablet computer and any other device that can be connected to the data center 50 .

The network 40 may be the Internet, a local area network or other communication networks.

The data center 50 is also connected to the database 30 via a database connection. Wherein, the database connection may be an open database connection (Open Database Connectivity, ODBC), or a Java database connection (Java Database Connectivity, JDBC).

The database 30 stores a file table and a version table, the version table is composed of the ID of the file and the version name of the file, and the file table is composed of the ID of the file, the name of the file, the version ID of the file and the URL of the file . The files uploaded by users are managed in the following two modes: the first one is managed in the form of basic files, the basic files refer to the files before the user modifies them, and the modification of the basic files will generate new version files, while The basic files will be kept. Through this mechanism, users' files can be protected and file redundancy can be avoided. The second is to manage in the form of a version file, the version file refers to the file obtained after modifying the base file, if the content of the version file is the same as that in the base file, then the URL of the version file points to the base file URL, in this way, to avoid uploading the same file again.

The relationship and structure between the basic file and the version file are illustrated by taking Figure 6 as an example. It can be seen from Figure 6 that the version file is generated by operating on the basic file and has a sequence relationship. Then extend this relationship as shown in Figure 7, the next version file will be generated for each version file operation, and the previous version file is the basic file for the next version file. Through this recursive architecture, the versions are associated with each other, so as to avoid redundant data.

Referring to FIG. 4 , it is a schematic structural diagram of a preferred embodiment of the data center 50 of the present invention. The data center 50 includes a file version control system 500 . It should be noted that since the data center 50 includes multiple servers, the file version control system 500 can be installed on a specific server in the data center 50, or can be installed on each server. In this preferred implementation In an example, the file version control system 500 is installed on a specific server in the data center. The file version control system 500 includes a creation module 510 and an operation module 520 . The module referred to in the present invention is a computer program segment that completes a specific function, which is more suitable than a program to describe the execution process of software in a computer, so the following description of software in the present invention is described as a module.

The creation module 510 is used to create a basic file, and the basic file is composed of a folder and files under the folder. The creation module 510 also saves the files under the folder to the database 30 . Suppose the folder name is FolderV1.0, and there are two files named file1 and file2 under it. File attributes include ID, file name, URL, modification date, and pointing ID (pointer), etc., as shown in Figure 8.

The operation module 520 is used to operate on basic files. The operations include addition, deletion and modification.

The creating module 510 is also configured to create a version file when the user completes the operation on the basic file and stores it. First, the creation module 510 generates a new folder according to the creation rules of the folder name. For example, according to the version number, the version number is increased by one each time a new version is created, for example, {FolderV1.0, FolderV2.0, FolderV3. 0,...,FolderVn.0}. When the version file folder is successfully created, the files under the version file folder will be generated. Specifically, all the files under the basic file are first obtained for the comparison in the next step. Taking Figure 8 as an example, two records of file1 and file2 under FolderV1.0 are obtained.

When the operation is modification, the unmodified part of the basic file is saved in the version file in the form of a pointer, and the modified part of the basic file is saved in the version file in the form of a file record. Specifically, when the user modifies the basic file, a folder of a version file is created according to the folder naming rules. Assuming that file2 is modified, the system will generate a version file folder such as FolderV2.0, as shown in Figure 9. There are still two files under FolderV2.0, file1 is a file that has not been modified, so a new pointer (pointer) is added, that is, the pointer 0001 of file1 is stored in FolderV2.0 in Figure 9 (it does not store its content , so as to avoid data redundancy), its pointing ID (that is, pointer) is 0001, which means that its attributes are exactly the same as those of file1 under FolderV1.0. And file2 is a modified file, so directly add a new file record to FolderV2.0, that is, the file name, ID, URL and modification date of file2 are stored in FolderV2.0 in Figure 9 .

When the operation is adding, the version file includes the pointer of the basic file and the newly added file record. Specifically, when the user adds a basic file, the addition is similar to the modification. When the user uploads file3 under FolderV2.0, a FolderV3.0 folder is created and a file record of file3 is directly added, while The original file1 and file2_V2.0 are changed to pointers, as shown in Figure 10. In addition, there is another situation, when the user wants to upload the file file3 to the FolderV1.0 folder instead of FolderV2.0, just add a pointer, as shown in Figure 11. When users want to know which data is modified from Folder V3.0, they only need to query its basic files.

When the operation is deletion, the version file contains a pointer to the base file. When the user deletes the base file, the delete operation does not remove the base file, but creates a new folder. As shown in Figure 12, after the user deletes file1 from FolderV3.0, a new version file FolderV4.0 is generated, wherein the file1 pointer in FolderV4.0 is removed and file3 is changed to a pointer.

As shown in FIG. 5 , it is a flow chart of a preferred embodiment of the file version control method of the present invention.

In step S10, the creation module 510 creates a basic file, and the basic file is composed of a folder and files under the folder. The creation module 510 also saves the files under the folder to the database 30 . Suppose the folder name is FolderV1.0, and there are two files named file1 and file2 under it. File attributes include ID, file name, URL, modification date, and pointing ID (pointer), etc., as shown in Figure 8.

In step S20, the operation module 520 is used to operate on the basic file. The operations include addition, deletion and modification.

Step S30, when the user completes the operation on the basic file and stores it, the creation module 510 creates a version file. First, the creation module 510 generates a new folder according to the creation rules of the folder name. For example, according to the version number, the version number is increased by one each time a new version is created, for example, {FolderV1.0, FolderV2.0, FolderV3. 0,...,FolderVn.0}. When the version file folder is successfully created, the files under the version file folder will be generated. Specifically, all the files under the basic file are first obtained for the comparison in the next step. Taking Figure 8 as an example, two records of file1 and file2 under FolderV1.0 are obtained.

When the operation is modification, the unmodified part of the basic file is saved in the version file in the form of a pointer, and the modified part of the basic file is saved in the version file in the form of a file record. Specifically, when the user modifies the basic file, a folder of a version file is created according to the folder naming rules. Assuming that file2 is modified, the system will generate a version file folder such as FolderV2.0, as shown in Figure 9. There are still two files under FolderV2.0, file1 is a file that has not been modified, so a new pointer (pointer) is added, that is, the pointer 0001 of file1 is stored in FolderV2.0 in Figure 9 (it does not store its content , so as to avoid data redundancy), its pointing ID (that is, pointer) is 0001, which means that its attributes are exactly the same as those of file1 under FolderV1.0. And file2 is a modified file, so directly add a new file record to FolderV2.0, that is, the file name, ID, URL and modification date of file2 are stored in FolderV2.0 in Figure 9 .

When the operation is adding, the version file includes the pointer of the basic file and the newly added file record. Specifically, when the user adds a basic file, the addition is similar to the modification. When the user uploads file3 under FolderV2.0, a FolderV3.0 folder is created and a file record of file3 is directly added, while The original file1 and file2_V2.0 are changed to pointers, as shown in Figure 10. In addition, there is another situation, when the user wants to upload the file file3 to the FolderV1.0 folder instead of FolderV2.0, just add a pointer, as shown in Figure 11. When users want to know which data is modified from Folder V3.0, they only need to query its basic files.

When the operation is deletion, the version file contains a pointer to the base file. When the user deletes the base file, the delete operation does not remove the base file, but creates a new folder. As shown in Figure 12, after the user deletes file1 from FolderV3.0, a new version file FolderV4.0 is generated, wherein the file1 pointer in FolderV4.0 is removed and file3 is changed to a pointer.

This method achieves the version control mechanism through a similar recursive concept, and uses folders to distinguish versions. The folder contains several files to achieve the purpose of multi-file version control. In addition, the combination of pointers eliminates the need to store two or more copies of the same file in the cloud storage space, and also ensures that the file has not been modified, saving storage space for the manufacturer. At the same time, under the service charged by storage space, this architecture can also save users' storage costs.

As shown in Figure 13, it is a user's operation interface. The upper block is the file operation area, including buttons such as upload, open, and delete. specific version starts). The middle block lists the files owned by the user, including the folder name and the files under the folder. In addition, the file list also contains related properties, such as folder name, file name, ID, URL and modification date, etc. Assume that the user currently stores two folders in the data center 50, namely Input_folder and Output_folder. Among them, the Input_folder contains two files, namely file1.txt and file2.txt, and the Output_folder is empty. The system reads file1.txt and file2.txt from Input_folder and takes out the data for processing. After the processing is completed, an output.txt file will be generated in the folder Output_folder, and the processing results will be printed on it, as shown in Figure 13.

In the above application scenario, suppose the user updates the input data, that is, add file3.txt under the Input_folder and modify the content of file2.txt. Under the framework of this method, a new version of Input_folder V2.0 will be generated and the original Input_folder will be retained, as shown in FIG. 14 . Through this mechanism, users can retain different processing results for analysis and comparison.

Claims (10)

1. A file version control system, which runs in a data center, is characterized in that the system includes: Create a module for creating a basic file, the basic file is composed of a folder and files under the folder; an operation module for operating on the underlying file; and The creation module is also used to create a version file when the user completes the basic file operation. The version file is generated by the operation of the basic file, has a sequence relationship and a recursive structure, and can be generated for each version file operation. For the next version file, the previous version file is the base file for the next version file, and the part that is repeated in the version file and the base file is saved as a pointer. 2. The file version control system according to claim 1, wherein the operations include deletion, modification and addition. 3. The file version control system according to claim 2, wherein when the operation is deletion, the version file includes a pointer to the base file. 4. The file version control system as claimed in claim 2, wherein when the operation is modification, the part that has not been modified in the basic file is saved in the version file in the form of a pointer, and the part that has not been modified in the basic file is saved The modified part is saved in the version file in the form of file record. 5. The file version control system according to claim 2, wherein when the operation is to add, the version file includes a pointer to the basic file and a newly added file record. 6. A file version control method, characterized in that the method comprises: Create a basic file, the basic file is composed of a folder and the files under the folder; operate on the underlying document; and When the user completes the operation of the basic file, the version file is created. The version file is generated by the operation of the basic file, and has a sequence relationship and a recursive structure. The next version file will be generated for each version file operation, and the next version file will be generated for the next version file. As far as the version file is concerned, the previous version file is the basic file, and the part that is repeated in the version file and the basic file is saved in the form of a pointer. 7. The file version control method according to claim 6, wherein the operations include deletion, modification and addition. 8. The file version control method according to claim 7, wherein when the operation is deletion, the version file includes a pointer to the base file. 9. The file version control method according to claim 7, wherein when the operation is modification, the part that has not been modified in the basic file is saved in the version file in the form of a pointer, and the part that has been modified in the basic file is saved to the version file. The modified part is saved in the version file in the form of file record. 10. The file version control method according to claim 7, wherein when the operation is to add, the version file includes a pointer to the basic file and a newly added file record.