CN117370270A - Data management method and device - Google Patents
Data management method and device Download PDFInfo
- Publication number
- CN117370270A CN117370270A CN202311226285.6A CN202311226285A CN117370270A CN 117370270 A CN117370270 A CN 117370270A CN 202311226285 A CN202311226285 A CN 202311226285A CN 117370270 A CN117370270 A CN 117370270A
- Authority
- CN
- China
- Prior art keywords
- file
- target
- directory
- deleted
- name
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000013523 data management Methods 0.000 title claims abstract description 46
- 238000012217 deletion Methods 0.000 claims description 13
- 230000037430 deletion Effects 0.000 claims description 13
- 238000012790 confirmation Methods 0.000 claims description 12
- 238000012986 modification Methods 0.000 claims description 3
- 230000004048 modification Effects 0.000 claims description 3
- 238000011084 recovery Methods 0.000 claims description 3
- 238000013473 artificial intelligence Methods 0.000 description 9
- 238000010586 diagram Methods 0.000 description 9
- 238000007726 management method Methods 0.000 description 9
- 238000013500 data storage Methods 0.000 description 6
- 238000004891 communication Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 4
- 238000001212 derivatisation Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 238000012549 training Methods 0.000 description 1
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/10—File systems; File servers
- G06F16/11—File system administration, e.g. details of archiving or snapshots
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/14—Details of searching files based on file metadata
- G06F16/148—File search processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/16—File or folder operations, e.g. details of user interfaces specifically adapted to file systems
- G06F16/162—Delete operations
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0638—Organizing or formatting or addressing of data
- G06F3/0643—Management of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
- G06F3/06—Digital input from, or digital output to, record carriers, e.g. RAID, emulated record carriers or networked record carriers
- G06F3/0601—Interfaces specially adapted for storage systems
- G06F3/0628—Interfaces specially adapted for storage systems making use of a particular technique
- G06F3/0646—Horizontal data movement in storage systems, i.e. moving data in between storage devices or systems
- G06F3/0652—Erasing, e.g. deleting, data cleaning, moving of data to a wastebasket
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Human Computer Interaction (AREA)
- Library & Information Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The disclosure provides a data management method and device. The method comprises the following steps: receiving a first file storage request, wherein the first file storage request comprises a first target file and a target directory, and the file name of the first target file is a target file name; writing the first target file into a source file directory; creating a first flexible connection file in a target directory, wherein the first flexible connection file points to a first target file in a source file directory, and the file name of the first flexible connection file is a target file name; and distributing version identifiers for the first target file and the first soft connection file.
Description
Technical Field
The disclosure relates to the field of communication technologies, and in particular, to a data management method and device.
Background
When using the AI (Artificial Intelligence) platform, a user creates a number of data sets (datasets) according to business needs. In the conventional data management method, each time a data set is created, a full copy of the data and a manual version record are associated, so that the problems of data expansion and derivatization are caused, more time and energy are required for users, and the data storage cost is exponentially increased.
Disclosure of Invention
In view of this, the present disclosure provides a data management method and apparatus, which is used to save time and effort of a user and reduce data storage cost.
In a first aspect, the present disclosure provides a data management method, the method comprising: receiving a first file storage request, wherein the first file storage request comprises a first target file and a target directory, and the file name of the first target file is a target file name; writing the first target file into a source file directory; creating a first flexible connection file in the target directory, wherein the first flexible connection file points to a first target file in the source file directory, and the file name of the first flexible connection file is the target file name; and distributing version identifiers for the first target file and the first soft connection file.
In a second aspect, the present disclosure provides a data management apparatus, the apparatus comprising: the first receiving module is used for receiving a first file storage request, wherein the first file storage request comprises a first target file and a target directory, and the file name of the first target file is a target file name; the first writing module is used for writing the first target file into a source file catalog; the first creating module is used for creating a first flexible connection file in the target directory, wherein the first flexible connection file points to a first target file in the source file directory, and the file name of the first flexible connection file is the target file name; and the first distribution module is used for distributing version identifiers for the first target file and the first soft connection file.
In a third aspect, the present disclosure provides a network device comprising a processor and a machine-readable storage medium storing machine-executable instructions executable by the processor to cause the processor to perform the method provided in the first aspect of the present disclosure.
Therefore, by applying the data management method and device provided by the disclosure, the target file to be stored is written into the source file directory, the soft connection file pointing to the target file is created in the target directory, and then the version identification is allocated for the target file and the soft connection file. Therefore, the method can automatically create the data, realize the version management of the data in a soft connection mode, save the time and energy of users, improve the efficiency of the version management of the data assets and reduce the cost of data storage.
Drawings
FIG. 1 is a schematic diagram of a system architecture shown in the present specification according to an exemplary embodiment;
FIG. 2 is a flow chart of a method for data management according to an embodiment of the present disclosure;
FIG. 3A is a schematic diagram of data management provided by an embodiment of the present disclosure;
FIG. 3B is a schematic diagram of data management according to another embodiment of the present disclosure;
FIG. 3C is a schematic diagram of data management according to another embodiment of the present disclosure;
fig. 4 is a data management apparatus according to an embodiment of the present disclosure;
fig. 5 is a hardware structure of a network device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present disclosure as detailed in the accompanying claims.
The terminology used in the present disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used in this disclosure and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term "and/or" as used herein refers to and encompasses any or all possible combinations of one or more of the corresponding listed items.
It should be understood that although the terms first, second, third, etc. may be used in this disclosure to describe various information, these information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of the present disclosure. The word "if" as used herein may be interpreted as "at … …" or "at … …" or "responsive to a determination", depending on the context.
The following describes a system architecture to which the data management method and apparatus of the present embodiment may be applied, with reference to fig. 1. It should be noted that fig. 1 is only an example of a system architecture to which embodiments of the present disclosure may be applied to assist those skilled in the art in understanding the technical content of the present disclosure, but does not mean that embodiments of the present disclosure may not be used in other devices, systems, environments, or scenarios.
Fig. 1 is a schematic diagram of a system architecture shown in the present specification according to an exemplary embodiment.
As shown in fig. 1, the system architecture may include, for example, terminal devices, networks, and servers. The network is used as a medium to provide a communication link between the terminal device and the server. The network may include various connection types, such as wired and/or wireless communication links, and the like.
The user may interact with the server via the network using the terminal device to receive or send messages or the like. Various communication client applications, such as a knowledge reading application, a web browser application, a search application, an instant messaging tool, a mailbox client and/or social platform software, etc., can be installed on the terminal device.
The terminal device may be a variety of electronic devices having a display screen and supporting web browsing, including but not limited to smartphones, tablets, laptop and desktop computers, and the like.
The server may be a server for data management. Such as a server that provides data management for the AI platform.
When using the AI platform, the user creates a number of data sets (datasets) according to the traffic demand. The server may perform data management on these data sets.
The data management method provided by the embodiment of the present disclosure is described in detail below. Referring to fig. 2, fig. 2 is a flowchart of a data management method according to an embodiment of the disclosure. The method is applied to data management, and the data management method provided by the embodiment of the disclosure can comprise the following steps.
Step 210, receiving a first file storage request, where the first file storage request includes a first target file and a target directory, and a file name of the first target file is a target file name.
According to the present disclosure, a first file storage request may be used to request a server to store a file. The first target file may be a file to be stored. The target directory may be a directory storing files.
Step 220, writing the first target file into the source file directory.
According to an embodiment of the present disclosure, a source file directory is a directory that actually stores files.
Step 230, creating a first flexible connection file in the target directory, wherein the first flexible connection file points to a first target file in the source file directory, and the file name of the first flexible connection file is the target file name.
According to the embodiment of the present disclosure, a file to be stored is not actually stored in a target directory, but is stored in a source file directory, a soft link file corresponding to the file is created in the target directory, and the file is pointed to, so that a user appears to have created the file in the target directory.
Step 240, a version identifier is allocated to the first target file and the first flexible connection file.
According to embodiments of the present disclosure, the version identification may be used to indicate the versions of the first target file and the first flexible connection file. It should be noted that the present disclosure is not limited to the type of version identification. Illustratively, in this embodiment, a version number may be used as the version identifier, where a higher version number indicates a higher version.
In the conventional data management method, each time a data set is created, a full copy of the data and a manual version record are associated, so that the problems of data expansion and derivatization are caused, more time and energy are required for users, and the data storage cost is exponentially increased.
According to an embodiment of the present disclosure, a target file to be stored is written into a source file directory, a flexible connection file pointing to the target file is created in the target directory, and then version identification is assigned to the target file and the flexible connection file. Therefore, the method can automatically create the data, realize the version management of the data in a soft connection mode, save the time and energy of users, improve the efficiency of the version management of the data assets and reduce the cost of data storage.
In addition, the data management method according to the embodiment of the present disclosure does not invade the original storage usage logic, and can quickly form flexible data version management capability through a small amount of development. And thus can be quickly integrated by third party platforms.
Illustratively, the data management method according to the embodiment of the present disclosure may be applied to an AI platform. Based on the above, the first target file can include, for example, a data set used by the AI platform, and version management of the data set is realized by adopting a soft connection mode, so that various versions can be quickly generated for the data set on the premise of not occupying excessive storage resources, and the method is convenient for different AI training scenes.
Alternatively, the version identification may be stored in meta-information of the first target file, for example. When the version identifier needs to be acquired, the version identifier can be acquired from meta information of the first target file. Illustratively, taking the Linux system as an example, the meta information of the file is included in the inode, based on which the version identification may be stored in the meta information included in the inode of the first target file.
Alternatively, the version identification of the file may be globally controlled, generating a unique version number for each version of the file, thereby ensuring data management consistency.
Alternatively, the user may query for the stored files. Based on this, the user may send a file query request to the server through the terminal device, and the file query request may include the target directory and the file name to be queried. And the server receives the file inquiry request, inquires the to-be-inquired soft connection file with the name of the to-be-inquired file name in the inquiry target directory, and outputs the to-be-inquired target file indicated by the to-be-inquired soft connection file.
Alternatively, the user may delete the file stored in the server. However, when the original file on which the flexible connection depends is deleted carelessly, all version connections allocated based on the original file cannot be used. In this embodiment, in order to prevent a user from deleting a file carelessly, when the user deletes a file of a certain version, the soft link file of the version is deleted, and the target file of the version is stored in the corresponding recycle bin directory, so that data cannot be deleted truly. Therefore, the problem of soft connection failure caused by misdeletion can be avoided.
Based on this, the user may send a first deletion request to the server through the terminal device, and the first deletion request may include the first file name to be deleted and the target directory. And the server receives the first deleting request, deletes the to-be-deleted soft connection file with the name of the first to-be-deleted file name in the target directory according to the first deleting request, and moves the to-be-recovered target file corresponding to the to-be-deleted soft connection file to the recovery station directory. Wherein the recycle bin directory can be set according to actual needs. In addition, in the case that the target file to be recycled has other soft link files except the soft link file to be deleted, the other soft link files are modified to point to the target file to be recycled in the recycle bin directory.
If the user wants to delete the file completely, the user can send a second deletion request to the server through the terminal device, so that the server deletes the target file in the recycle bin directory. Wherein the second delete request may include a second file name to be deleted and a recycle bin directory. The server receives a second delete request. And aiming at the target file to be deleted, the file name of which is the second file name to be deleted, in the recycle bin directory, if the target file to be deleted does not have soft connection dependence, deleting the target file to be deleted in the recycle bin directory. And if the target file to be deleted has soft connection dependency, displaying the deleting prompt information. The deletion prompt information can be used for prompting the user whether to truly delete the target file to be deleted, and the user can send a confirmation deletion instruction after confirmation. And the server receives a confirmation deleting instruction corresponding to the deleting prompt information. And then deleting the target file to be deleted in the recycle bin directory according to the confirmation deleting instruction. If the user does not send the confirmation deleting instruction, the server does not delete the target file to be deleted.
Alternatively, after the user deletes the soft link file in the target directory, the file having the same file name as the soft link file may be further stored. Based on the file, the user can send a second file storage request to the server through the terminal equipment, wherein the second file storage request comprises a second target file and a target directory, and the file name of the second target file is the first file name to be deleted. The server receives a second file storage request, writes a second target file into the source file directory, and creates a second flexible connection file in the target directory, wherein the second flexible connection file points to the second target file in the source file directory, and the file name of the second flexible connection file is the first file name to be deleted. If the original target file with the file name being the first file name to be deleted exists in the recycle bin directory, a new version identifier is allocated to the second target file, and the version indicated by the new version identifier is higher than the version indicated by the version identifier of the original target file. If the original target file with the file name of the first file name to be deleted does not exist in the recycle bin directory, any version identification can be allocated to the second target file. For example, in this embodiment, the initial version identifier may be preset, and based on this, in a case where there is no original target file with a file name of the first file name to be deleted in the recycle bin directory, the initial version identifier may be allocated to the second target file.
The data management method provided by the embodiments of the present disclosure is described in more detail below in conjunction with specific embodiments and fig. 3A-3C.
Illustratively, in this embodiment, the server may be based on the Linux system.
Fig. 3A is a schematic diagram of data management according to an embodiment of the disclosure. As shown in fig. 3A, the AI development platform intends to create a data set dataset v1 and add a target file a therein, based on which the AI development platform can send a file storage request to the server, the file storage request including the target file a and the target directory dataset v1. After the server receives the file storage request, a target file a is created in a root directory (source file directory): root/a. The Version number (Version) 111 is added to the file metadata information included in the inode of the target file a. For the target file a of version 111, its actual data is stored in block. For distinction, the target file a in block is hereinafter referred to as the a-111 file.
Fig. 3B is a schematic diagram of data management according to another embodiment of the present disclosure. As shown in fig. 3B, the server may create a dataset v1, in which a soft link file a is added, and a corresponding soft connection is established: dataset/v1/a- >/root/a.
If the user carelessly deletes/root/a, the version of/root/a is 111, the version is: the target files a-111 of 111 are stored in the corresponding recycle bin directory without actually deleting the data and affecting the flexible connection of the target files. If the user wants to delete the file completely, a delete function is provided in the recycle bin. When deleting the target file in the recycle bin, the user can firstly judge whether the target file has soft connection dependence. If so, a deletion prompt message is displayed to prompt the user whether to confirm the deletion. After the confirmation deleting instruction of the user is obtained, the file is deleted. If not, the target file can be deleted directly.
Fig. 3C is a schematic diagram of data management according to another embodiment of the present disclosure. As shown in fig. 3C, after the user deletes/root/a carelessly, the user cannot see/root/a, and if the user re-creates/root/a again later, the version is calculated globally, and if the target file of version 111 is found in the recycle bin, the creation version number is increased, for example verison:222, to the newly created/root/a. For distinction purposes, the target file a in block version 222 is hereinafter referred to as the a-222 file.
When the user queries for file a, the server returns the latest version of the a-222 file.
According to the embodiment of the disclosure, when a user deletes a file, the soft link file of a corresponding version is deleted, and the target file of the version is stored in the corresponding recycle bin directory, so that data cannot be truly deleted, the soft connection of the target file is not affected, and the problem of soft connection failure caused by misdeletion can be avoided.
Based on the same inventive concept, the embodiment of the disclosure also provides a data management device corresponding to the data management method. Referring to fig. 4, fig. 4 is a schematic diagram of a data management apparatus according to an embodiment of the present disclosure, where the apparatus may be applied to a server, and the data management apparatus may include;
the first receiving module 410 may be configured to receive a first file storage request, where the first file storage request includes a first target file and a target directory, and a file name of the first target file is a target file name;
a first write module 420 that can be used to write a first target file to a source file directory;
the first creating module 430 may be configured to create a first flexible connection file in the target directory, where the first flexible connection file points to a first target file in the source file directory, and a file name of the first flexible connection file is a target file name;
the first allocation module 440 may be configured to allocate a version identifier for the first target file and the first flexible connection file.
Optionally, the data management apparatus may further include:
the second receiving module is used for receiving a file query request, wherein the file query request comprises a target directory and a file name to be queried;
the query module is used for querying the to-be-queried soft connection file with the name of the to-be-queried file name in the target directory;
and the output module is used for outputting the target file to be queried indicated by the soft link file to be queried.
Optionally, the data management apparatus may further include:
the third receiving module is used for receiving a first deleting request, wherein the first deleting request comprises a first file name to be deleted and a target directory;
the first deleting module is used for deleting the to-be-deleted flexible connection file with the name of the first to-be-deleted file name in the target directory according to the first deleting request, and moving the to-be-recovered target file corresponding to the to-be-deleted flexible connection file to the recycle bin directory;
and the modification module is used for modifying other soft link files to point to the target file to be recycled in the recycle bin directory under the condition that the target file to be recycled has other soft link files except the soft link file to be deleted.
Optionally, the data management apparatus may further include:
the fourth receiving module is used for receiving a second deleting request, and the second deleting request comprises a second file name to be deleted and a recycle bin directory;
the second deleting module is used for deleting the target file to be deleted in the recycle bin directory aiming at the target file to be deleted with the file name of the second target file to be deleted in the recycle bin directory, if the target file to be deleted does not have soft connection dependence;
the display module is used for displaying the deleting prompt information if the target file to be deleted has soft connection dependence;
the instruction receiving module is used for receiving a confirmation deleting instruction corresponding to the deleting prompt information;
and the third deleting module is used for deleting the target file to be deleted in the recycle bin directory according to the confirmation deleting instruction.
Optionally, the data management apparatus may further include:
the fifth receiving module is used for receiving a second file storage request after deleting the soft connection file to be deleted, wherein the second file storage request comprises a second target file and a target directory, and the file name of the second target file is the first file name to be deleted;
the second writing module is used for writing a second target file into the source file catalog;
the second creating module is used for creating a second soft connection file in the target directory, the second soft connection file points to a second target file in the source file directory, and the file name of the second soft connection file is a first file name to be deleted;
and the second allocation module is used for allocating a new version identifier for the second target file if the original target file with the file name of the first file name to be deleted exists in the recycle bin directory, and the version indicated by the new version identifier is higher than the version indicated by the version identifier of the original target file.
According to an embodiment of the present disclosure, a target file to be stored is written into a source file directory, a flexible connection file pointing to the target file is created in the target directory, and then version identification is assigned to the target file and the flexible connection file. Therefore, the method can automatically create the data, realize the version management of the data in a soft connection mode, save the time and energy of users, improve the efficiency of the version management of the data assets and reduce the cost of data storage.
In addition, the data management method according to the embodiment of the present disclosure does not invade the original storage usage logic, and can quickly form flexible data version management capability through a small amount of development. And thus can be quickly integrated by third party platforms.
Based on the same inventive concept, the disclosed embodiment also provides a network device, as shown in fig. 5, including a processor 510, a transceiver 520, and a machine-readable storage medium 530, the machine-readable storage medium 530 storing machine executable instructions capable of being executed by the processor 510, the processor 510 being caused by the machine executable instructions to perform the data management method provided by the disclosed embodiment. The data management apparatus shown in fig. 4 may be implemented by using a hardware structure of a network device as shown in fig. 5.
The computer readable storage medium 530 may include a random access Memory (hereinafter referred to as "RAM") or a nonvolatile Memory (hereinafter referred to as "Non-volatile Memory") such as at least one magnetic disk Memory. Optionally, the computer readable storage medium 530 may also be at least one storage device located remotely from the aforementioned processor 510.
The processor 510 may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; it may also be a digital signal processor (English: digital Signal Processor; DSP; for short), an application specific integrated circuit (English: application Specific Integrated Circuit; ASIC; for short), a Field programmable gate array (English: field-Programmable Gate Array; FPGA; for short), or other programmable logic device, discrete gate or transistor logic device, discrete hardware components.
In the presently disclosed embodiments, processor 510 is enabled by reading machine-executable instructions stored in machine-readable storage medium 530, which cause processor 510 itself to be implemented and transceiver 520 to be invoked to perform the data management methods described in the presently disclosed embodiments.
Additionally, the disclosed embodiments provide a machine-readable storage medium 530, the machine-readable storage medium 530 storing machine-executable instructions that, when invoked and executed by the processor 510, cause the processor 510 itself and the invoking transceiver 520 to perform the data management methods described in the foregoing disclosed embodiments.
The implementation process of the functions and roles of each unit in the above device is specifically shown in the implementation process of the corresponding steps in the above method, and will not be described herein again.
For the device embodiments, reference is made to the description of the method embodiments for the relevant points, since they essentially correspond to the method embodiments. The apparatus embodiments described above are merely illustrative, wherein the elements illustrated as separate elements may or may not be physically separate, and the elements shown as elements may or may not be physical elements, may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the objectives of the disclosed solution. Those of ordinary skill in the art will understand and implement the present invention without undue burden.
For the data management device and the machine-readable storage medium embodiments, since the method content involved is substantially similar to the method embodiments described above, the description is relatively simple, and reference will only be made to the part of the description of the method embodiments where relevant.
The foregoing description of the preferred embodiments of the present disclosure is not intended to limit the disclosure, but rather to cover all modifications, equivalents, improvements and alternatives falling within the spirit and principles of the present disclosure.
Claims (10)
1. A method of data management, the method comprising:
receiving a first file storage request, wherein the first file storage request comprises a first target file and a target directory, and the file name of the first target file is a target file name;
writing the first target file into a source file directory;
creating a first flexible connection file in the target directory, wherein the first flexible connection file points to a first target file in the source file directory, and the file name of the first flexible connection file is the target file name;
and distributing version identifiers for the first target file and the first soft connection file.
2. The method according to claim 1, wherein the method further comprises:
receiving a file query request, wherein the file query request comprises the target directory and a file name to be queried;
inquiring a to-be-inquired soft connection file with the name of the to-be-inquired file name in the target directory;
and outputting the target file to be queried indicated by the soft link file to be queried.
3. The method according to claim 1, wherein the method further comprises:
receiving a first deletion request, wherein the first deletion request comprises a first file name to be deleted and the target directory;
deleting the to-be-deleted soft connection file with the name of the first to-be-deleted file name in the target directory according to the first deletion request, and moving the to-be-recovered target file corresponding to the to-be-deleted soft connection file to a recovery station directory;
and when the target file to be recycled has other soft link files except the soft link file to be deleted, modifying the other soft link files to point to the target file to be recycled in the recycle bin directory.
4. A method according to claim 3, characterized in that the method further comprises:
receiving a second deletion request, wherein the second deletion request comprises a second file name to be deleted and the recycle bin directory;
aiming at the target file to be deleted, the file name of which is the second file name to be deleted, in the recycle bin directory, if the target file to be deleted does not have soft connection dependence, deleting the target file to be deleted in the recycle bin directory;
if the target file to be deleted has soft connection dependence, displaying deletion prompt information;
receiving a confirmation deleting instruction corresponding to the deleting prompt information;
and deleting the target file to be deleted in the recycle bin directory according to the confirmation deleting instruction.
5. A method according to claim 3, wherein after deleting the soft connection file to be deleted, the method further comprises:
receiving a second file storage request, wherein the second file storage request comprises a second target file and a target directory, and the file name of the second target file is the first file name to be deleted;
writing the second target file into the source file directory;
creating a second flexible connection file in the target directory, wherein the second flexible connection file points to a second target file in the source file directory, and the file name of the second flexible connection file is the first file name to be deleted;
and if the original target file with the file name of the first file name to be deleted exists in the recycle bin directory, a new version identifier is allocated to the second target file, and the version indicated by the new version identifier is higher than the version indicated by the version identifier of the original target file.
6. A data management apparatus, the apparatus comprising;
the first receiving module is used for receiving a first file storage request, wherein the first file storage request comprises a first target file and a target directory, and the file name of the first target file is a target file name;
the first writing module is used for writing the first target file into a source file catalog;
the first creating module is used for creating a first flexible connection file in the target directory, wherein the first flexible connection file points to a first target file in the source file directory, and the file name of the first flexible connection file is the target file name;
and the first distribution module is used for distributing version identifiers for the first target file and the first soft connection file.
7. The apparatus of claim 6, wherein the apparatus further comprises:
the second receiving module is used for receiving a file query request, wherein the file query request comprises the target directory and a file name to be queried;
the query module is used for querying the to-be-queried soft connection file with the name of the to-be-queried file name in the target directory;
and the output module is used for outputting the target file to be queried indicated by the soft link file to be queried.
8. The apparatus of claim 6, wherein the apparatus further comprises:
the third receiving module is used for receiving a first deleting request, wherein the first deleting request comprises a first file name to be deleted and the target directory;
the first deleting module is used for deleting the to-be-deleted soft connection file with the name of the first to-be-deleted file name in the target directory according to the first deleting request, and moving the to-be-recovered target file corresponding to the to-be-deleted soft connection file to a recovery station directory;
and the modification module is used for modifying the other soft link files to point to the target file to be recycled in the recycle bin directory under the condition that the target file to be recycled has other soft link files except the soft link file to be deleted.
9. The apparatus of claim 8, wherein the apparatus further comprises:
the fourth receiving module is used for receiving a second deleting request, and the second deleting request comprises a second file name to be deleted and the recycle bin directory;
the second deleting module is used for deleting the target file to be deleted in the recycle bin directory if the target file to be deleted does not have soft connection dependency aiming at the target file to be deleted with the file name in the recycle bin directory being the second file name to be deleted;
the display module is used for displaying deleting prompt information if the target file to be deleted has soft connection dependence;
the instruction receiving module is used for receiving a confirmation deleting instruction corresponding to the deleting prompt information;
and the third deleting module is used for deleting the target file to be deleted in the recycle bin directory according to the confirmation deleting instruction.
10. The apparatus of claim 8, wherein the apparatus further comprises:
the fifth receiving module is used for receiving a second file storage request after deleting the soft connection file to be deleted, wherein the second file storage request comprises a second target file and a target directory, and the file name of the second target file is the first file name to be deleted;
a second writing module, configured to write the second target file into the source file directory;
the second creating module is used for creating a second soft connection file in the target directory, wherein the second soft connection file points to a second target file in the source file directory, and the file name of the second soft connection file is the first file name to be deleted;
and the second allocation module is used for allocating a new version identifier for the second target file if the original target file with the file name being the first file name to be deleted exists in the recycle bin directory, wherein the version indicated by the new version identifier is higher than the version indicated by the version identifier of the original target file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311226285.6A CN117370270A (en) | 2023-09-21 | 2023-09-21 | Data management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311226285.6A CN117370270A (en) | 2023-09-21 | 2023-09-21 | Data management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117370270A true CN117370270A (en) | 2024-01-09 |
Family
ID=89390157
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311226285.6A Pending CN117370270A (en) | 2023-09-21 | 2023-09-21 | Data management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117370270A (en) |
-
2023
- 2023-09-21 CN CN202311226285.6A patent/CN117370270A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11586506B2 (en) | System and method for indexing image backups | |
| CN110018998B (en) | File management method and system, electronic equipment and storage medium | |
| US11762832B2 (en) | Container storage management system | |
| CN104391725A (en) | Page display method and page display device | |
| US7584209B2 (en) | Flexible file format for updating an address book | |
| CN105474206A (en) | Virtual synchronization with on-demand data delivery | |
| KR20100133380A (en) | Computing environment representation | |
| JP2005521946A (en) | Method and apparatus for synchronizing with respect to techniques for storing data in different data storage units | |
| US11687595B2 (en) | System and method for searching backups | |
| CN107103011B (en) | Method and device for realizing terminal data search | |
| US20190155798A1 (en) | Cache management | |
| US11574025B2 (en) | Systems and methods for managed asset distribution in a distributed heterogeneous storage environment | |
| CN110555015A (en) | Database entity management method and device, electronic equipment and storage medium | |
| CN105227672A (en) | The method and system that data store and access | |
| US7478118B2 (en) | Method and apparatus for synchronizing of databases connected by wireless interface | |
| US8082230B1 (en) | System and method for mounting a file system on multiple host computers | |
| CN109729121B (en) | Cloud storage system and method for realizing custom data processing in cloud storage system | |
| EP3343395A1 (en) | Data storage method and apparatus for mobile terminal | |
| CN112579877A (en) | Information source system control method, device, storage medium and equipment | |
| CN117370270A (en) | Data management method and device | |
| US9936015B2 (en) | Method for building up a content management system | |
| US20220237176A1 (en) | Method and system for managing changes of records on hosts | |
| CN109857719B (en) | Distributed file processing method, device, computer equipment and storage medium | |
| CN109325057B (en) | Middleware management method, device, computer equipment and storage medium | |
| CN111488324A (en) | Distributed network file system based on message middleware and working method thereof |
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 |